Changes between Version 2 and Version 3 of Windows_Kernel_Debugging

Timestamp:

Jun 6, 2011 12:31:22 PM (14 years ago)

Author:

Frank Mehnert

Comment:

--

Windows_Kernel_Debugging

@@ -22 +22 @@
  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].
    - Both 32bit and 64bit versions of Debugging Tools could be used for debugging both 32bit and 64bit Targets.
- 1. Run the WinDbg debugger: "Start"->"All Programs"->"Debugging Tools For Windows"->"WinDbg".
- 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"
+ 1. Run the !WinDbg debugger: "Start"->"All Programs"->"Debugging Tools For Windows"->"!WinDbg".
+ 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"
    - 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.
 
@@ -34 +34 @@
 
 === Host Computer ===
- 1. Run the WinDbg debugger: "Start"->"All Programs"->"Debugging Tools For Windows"->"WinDbg".
+ 1. Run the !WinDbg debugger: "Start"->"All Programs"->"Debugging Tools For Windows"->"!WinDbg".
    - 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.
- 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"
-   - The first time you do it you'll see some progress while WinDbg is installing the 1394d driver.
+ 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"
+   - The first time you do it you'll see some progress while !WinDbg is installing the 1394d driver.
    - Finally windbg should print something like
 {{{
@@ -49 +49 @@
 
 == Common Kernel Debugging Tasks ==
-NOTE: unless otherwise specified all the tasks here list the WinDbg commands that should be entered in a debugger command window.
+NOTE: unless otherwise specified all the tasks here list the !WinDbg commands that should be entered in a debugger command window.
 The command window becomes active only when the debuggee is break in the debugger.
 To force the target system to break use <ctrl>+<break>, to resume use "g" command (in a debugger command window ofc)
 
-=== Creating a dump file with WinDbg ===
+=== Creating a dump file with !WinDbg ===
  1. Minidump
 {{{
@@ -62 +62 @@
 .dump /f <dump\file\path\on\the\host\system.dmp>
 }}}
- 1. Kernel memory dump - it's not possible to do that with WinDbg
+ 1. Kernel memory dump - it's not possible to do that with !WinDbg