1: Set up. EXE is extremely PDB, which is placed in the same directory or a directory that can be found by windbg.
2: Enable windbg and F5 to run.
3: When a breakpoint or process exception occurs, control is returned to windbg,
1 ):
Click the callstack command in the toolbar,
Open the Stack window and you can see the function call stack,
2)
Click the source command in the new callstack window to display the location and row number of the source file corresponding to the function in the stack. (If your source file is placed here, it will be directly transferred to your source file .)
The callstack window also provides a lot of information for viewing. For example, funcinfo can see the call Convention stdcall for this function, frame Nums can see the frame number. sourceargs, and the original parameters.
4: click "local". The exception is the field variable.
See:
Windows ApplicationsProgramDebugging Policy (1)
Http://dev.csdn.net/Develop/article/21/21915.shtm
Windows application debugging Policy (2)
...