VirtualBox

Changes between Version 2 and Version 3 of Windows_Kernel_Debugging


Ignore:
Timestamp:
06/06/11 12:31:22 (3 years ago)
Author:
frank
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Windows_Kernel_Debugging

    v2 v3  
    2222 1. Install Debugging Tools For Windows. You can install it as a stand-alone component from the Windows SDK in a way described [http://msdn.microsoft.com/en-us/windows/hardware/gg463009 here]. 
    2323   - Both 32bit and 64bit versions of Debugging Tools could be used for debugging both 32bit and 64bit Targets. 
    24  1. Run the WinDbg debugger: "Start"->"All Programs"->"Debugging Tools For Windows"->"WinDbg". 
    25  1. Setup WinDbg symbol paths: "File"->"Symbol File Path" -> in the "Symbol File Path" dialog enter "srv*c:\symbols*http://msdl.microsoft.com/download/symbols" (w/o quotes) in the edit box->"OK" 
     24 1. Run the !WinDbg debugger: "Start"->"All Programs"->"Debugging Tools For Windows"->"!WinDbg". 
     25 1. Setup !WinDbg symbol paths: "File"->"Symbol File Path" -> in the "Symbol File Path" dialog enter "srv*c:\symbols*http://msdl.microsoft.com/download/symbols" (w/o quotes) in the edit box->"OK" 
    2626   - NOTE: the C:\symbols here is the path of your downstream store, i.e. the path where the downloaded symbols would be stored/cached. You can use any path for that. 
    2727 
     
    3434 
    3535=== Host Computer === 
    36  1. Run the WinDbg debugger: "Start"->"All Programs"->"Debugging Tools For Windows"->"WinDbg". 
     36 1. Run the !WinDbg debugger: "Start"->"All Programs"->"Debugging Tools For Windows"->"!WinDbg". 
    3737   - NOTE: you need to run it with elevated privileges (i.e. "Run As Administrator") the first time you want to setup a 1394 kernel debugging so that it is able to install the necessary 1394 debugging driver. 
    38  1. For 1394 debugging: in WinDbg do: "File"->"Kernel Debug"->open "1394" tab and type "10" (w/o quotes) in the "Chanel" edit box->press "OK" 
    39    - The first time you do it you'll see some progress while WinDbg is installing the 1394d driver. 
     38 1. For 1394 debugging: in !WinDbg do: "File"->"Kernel Debug"->open "1394" tab and type "10" (w/o quotes) in the "Chanel" edit box->press "OK" 
     39   - The first time you do it you'll see some progress while !WinDbg is installing the 1394d driver. 
    4040   - Finally windbg should print something like 
    4141{{{ 
     
    4949 
    5050== Common Kernel Debugging Tasks == 
    51 NOTE: unless otherwise specified all the tasks here list the WinDbg commands that should be entered in a debugger command window. 
     51NOTE: unless otherwise specified all the tasks here list the !WinDbg commands that should be entered in a debugger command window. 
    5252The command window becomes active only when the debuggee is break in the debugger. 
    5353To force the target system to break use <ctrl>+<break>, to resume use "g" command (in a debugger command window ofc) 
    5454 
    55 === Creating a dump file with WinDbg === 
     55=== Creating a dump file with !WinDbg === 
    5656 1. Minidump 
    5757{{{ 
     
    6262.dump /f <dump\file\path\on\the\host\system.dmp> 
    6363}}} 
    64  1. Kernel memory dump - it's not possible to do that with WinDbg 
     64 1. Kernel memory dump - it's not possible to do that with !WinDbg 

www.oracle.com
ContactPrivacy policyTerms of Use