Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \\.\pipe\com_1
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target at (Sat Aug 28 11:49:44.156 2010 (UTC + 8:00)), ptr64 FALSE
Kernel Debugger connection established. (Initial Breakpoint requested)
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlpa.exe -
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070227-2300
Machine Name:
Kernel base = 0x804d8000 PsLoadedModuleList = 0x805545a0
Debug session time: Sat Aug 28 11:49:38.906 2010 (UTC + 8:00)
System Uptime: 0 days 0:00:58.531
Break instruction exception - code 80000003 (first chance)
*******************************************************************************
* *
* You are seeing this message because you pressed either *
* CTRL+C (if you run kd.exe) or, *
* CTRL+BREAK (if you run WinDBG), *
* on your debugger machine's keyboard. *
* *
* THIS IS NOT A BUG OR A SYSTEM CRASH *
* *
* If you did not intend to break into the debugger, press the "g" key, then *
* press the "Enter" key now. This message might immediately reappear. If it *
* does, press "g" and "Enter" again. *
* *
*******************************************************************************
nt!DbgBreakPointWithStatus+0x4:
8052816c cc int 3
kd> .reload
Connected to Windows XP 2600 x86 compatible target at (Sat Aug 28 11:50:02.921 2010 (UTC + 8:00)), ptr64 FALSE
Loading Kernel Symbols
...............................................................
................................................
Loading User Symbols
Loading unloaded module list
........
*** WARNING: Unable to verify timestamp for vmx_fb.dll
*** ERROR: Module load completed but symbols could not be loaded for vmx_fb.dll
*** ERROR: Module load completed but symbols could not be loaded for kmixer.sys
*** ERROR: Module load completed but symbols could not be loaded for hgfs.sys
*** ERROR: Module load completed but symbols could not be loaded for ipnat.sys
*** ERROR: Module load completed but symbols could not be loaded for ipsec.sys
*** ERROR: Module load completed but symbols could not be loaded for isapnp.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for vmx_svga.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for drmk.sys -
*** ERROR: Module load completed but symbols could not be loaded for vmxnet.sys
*** ERROR: Module load completed but symbols could not be loaded for vmmemctl.sys
*** ERROR: Module load completed but symbols could not be loaded for vmscsi.sys
*** ERROR: Module load completed but symbols could not be loaded for intelide.sys
*** ERROR: Module load completed but symbols could not be loaded for vmmouse.sys
终于放假了,花了三天的时间,现在终于解决了。 是VS2005环境配置的有问题。之前配置的环境,可以编译得到符号表和驱动程序,而且驱动程序可以被正常的加载和执行。但符号表可能在编译的时候由于环境配置的原因不能被加载到WINDBG中。
Without you, life sometimes is so difficult.....