12.07.2015 Views

Bug Hunter Diary

Bug Hunter Diary

Bug Hunter Diary

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Information CommandsCommandrkbu addressDescriptionLists registers and their contents.Prints a backtrace of all stack frames.Dumps a range of memory around address as machineinstructions.Other CommandsCommand!analyze -v!drvobj DRIVER_OBJECT.sympath.reloadDescriptionThis debugger extension displays a lot of useful informationabout an exception or bug check.This debugger extension displays detailed informationabout a DRIVER_OBJECT.This command changes the default path of the debuggerfor symbol search.This command deletes all symbol information andreloads these symbols as needed.B.3 windows Kernel DebuggingIn order to analyze the vulnerability described in Chapter 6, I neededa way to debug the Windows kernel. I set up a debugging environmentwith VMware 2 and WinDbg 3 by following these steps:• Step 1: Configure the VMware guest system forremote kernel debugging.• Step 2: Adjust the boot.ini of the guest system.• Step 3: Configure WinDbg on the VMware hostfor Windows kernel debugging.← Throughout thissection, I used thefollowing softwareversions: VMwareWorkstation 6.5.2and WinDbg6.10.3.233.Step 1: Configure the VMware Guest System for Remote KernelDebuggingAfter I installed a Windows XP SP3 VMware guest system, I powered itoff and chose Edit Virtual Machine Settings from the Commands sectionof VMware. I then clicked the Add button to add a new serial portand chose the configuration settings shown in Figures B-1 and B-2.Debugging 167

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!