Some precautions for windbg local win7 debugging!

Use windbg for kernel debugging and do a few things

1. Run bcdedit-Debug on to enable debugging, and restart to take effect.

2. Download the symbol package to the http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx

Windows 7 RC x86 retail symbols, All Versions

3. Add the Environment Variable _ nt_symbol_path as the installation path of the symbol package.

Run windbg as an administrator to debug the kernel 7.

 

// The specific process is as follows:

1. in VMware, add SerialPort (\. PIPE \ com_1). Refer to the configuration in XP;
2. boot.ini is missing in win7. use the bcdedit.exe command line to configure it (the only difference from the past );
3. Copy the current configuration;
Bcdedit/copy {current}/D "Windows 7 debug"
4. Record the guid of the newly added identifier;
Bcdedit
5. Added debugging functions for newly added startup items;
Bcdedit/debug {previously queried guid} on
6. Modify debugging settings;
Bcdedit/dbgsettings serial debugport: 1 baudrate: 115200
7. Add a windbg shortcut to the outer system and modify its command behavior (note that the installation path must correspond to your local computer ).
"C: \ Program Files \ debugging tools for Windows (x86) \ windbg.exe"-B-K COM: Port =\\\ PIPE \ com_1, baud = 115200, pipe

Remember: cmd.exe must run with the Administrator permission. Other settings are the same as debugging the XP system!

In addition, the following blog post is more detailed and illustrated in red.

Http://yexin218.iteye.com/blog/545187

Problems:ProgramAfter the INT 3 breakpoint is broken, the normal program context is not displayed, and the windbg is always in the busy state ......

Solution:Run bcdedit-Debug on to enable debugging. the restart takes effect!