1.0

You will use the following specific WinDbg commands and menu items, in addition to the familiar debugger commands of Go, Step, Watch, and so on:

Command Meaning

File, then Open Executable Brings up your program inside the WinDbg debugger. This allows you to debug the initialization phases of your program's execution. However, the program's memory usage is somewhat different from that of ordinary execution. File, then Attach to a Process Links the WinDbg debugger to your program after it has started running. You cannot debug the initialization phases of your program's execution. However, the program's memory usage is more similar to that of ordinary execution than if you had brought up the program inside the debugger. File, then Symbol File Path Directs the WinDbg debugger to the directories in which the VC++ compiler has placed the debug (.pdb) files that your program needs to display symbols, such as subprogram names. File, then Source File Path Directs the WinDbg debugger to the directories in which the source files for your program reside. .symfix+ Turns on access to the Microsoft online symbol server. The resulting path appears in the Symbol File Path. You must be connected to the Web for this command to work. .dump /ma Filename.dmp Dumps heap memory in mini-dump format. The /ma option means it is a mini-dump (/m...) containing all (...a) information needed to reconstruct the state of the program when the dump occurred. File, then Open Crash Dump Directs the WinDbg debugger to a dump file produced by the .dump command. !analyze -v Analyzes the contents of a dump file produced by the .dump command. The -v stands for "verbose" information.