“MyDriver” was not found in the image list.
Debugger will attempt to load “MyDriver” at given base 00000000`00000000.
Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=,. DBGENG: MyDriver - Partial symbol image load missing image info DBGHELP: No header for MyDriver. Searching for dbg file …
After step D I can see and use the symbols belonging to MyDriver.
Questions : how could I achieve a clean situation, not requiring the steps B and C above? Is my problem likely to be with the with the driver build settings, or with the installation of debug tools? On target? On Debugger?
Thank you for help.
Notes :
Build + Debugger PC runs WinXP Target PC runs Win7
Full C:\WINDDK\7600.16385.1 is installed on each PC (32 or 64 bit as appropriate) WinDbg connection is COM1 115200 baud
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Friday, August 13, 2010 12:09 PM
To: Kernel Debugging Interest List
Subject: [windbg] “Partial symbol image load missing image info”
Hello
I’m trying to set up the WinDbg for remote debugging of a wdf driver under
development.
On Ctrl-Break in WinDbg the target system halts and …
“MyDriver” was not found in the image list.
Debugger will attempt to load “MyDriver” at given base 00000000`00000000.
Please provide the full image name, including the extension (i.e.
kernel32.dll) for more reliable results.Base address and size overrides can
be given as .reload <image.ext>=,. DBGENG: MyDriver - Partial symbol image load missing image info DBGHELP: No header for MyDriver. Searching for dbg file …
After step D I can see and use the symbols belonging to MyDriver.
Questions : how could I achieve a clean situation, not requiring the steps B and C above? Is my problem likely to be with the with the driver build settings, or with the installation of debug tools? On target? On Debugger?
Thank you for help.
Notes :
Build + Debugger PC runs WinXP Target PC runs Win7
Full C:\WINDDK\7600.16385.1 is installed on each PC (32 or 64 bit as appropriate) WinDbg connection is COM1 115200 baud