Difference between revisions of "Windbg"

(New page: Here are a few tips for using Windbg.)
 
Line 1: Line 1:
 
Here are a few tips for using Windbg.
 
Here are a few tips for using Windbg.
 +
 +
=== Debugging a 32-bit application on 64-bit windows ===
 +
 +
Have a look at: http://msdn.microsoft.com/en-us/library/aa384163(v=vs.85).aspx
 +
 +
To summarize one has to use:
 +
 +
* '''!wow64exts.sw''': Switches between x86 and native mode.
 +
* '''!wow64exts.k [count]''': Dumps a combined 32-bit/64-bit stack trace. If `count' is specified, the command dumps the first count addresses in each stack trace.
 +
* '''!wow64exts.info''': Dumps basic information about the PEB of the process, the TEB of the current thread, and thread local storage (TLS) slots used by WOW64.
 +
* '''!wow64exts.r [address]''': Dumps context for the specified address. If address is not specified, the command dumps context for the processor.

Revision as of 15:57, 14 February 2011

Here are a few tips for using Windbg.

Debugging a 32-bit application on 64-bit windows

Have a look at: http://msdn.microsoft.com/en-us/library/aa384163(v=vs.85).aspx

To summarize one has to use:

  • !wow64exts.sw: Switches between x86 and native mode.
  • !wow64exts.k [count]: Dumps a combined 32-bit/64-bit stack trace. If `count' is specified, the command dumps the first count addresses in each stack trace.
  • !wow64exts.info: Dumps basic information about the PEB of the process, the TEB of the current thread, and thread local storage (TLS) slots used by WOW64.
  • !wow64exts.r [address]: Dumps context for the specified address. If address is not specified, the command dumps context for the processor.