"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 …

A- examine : fails
kd> x MyDriver!*
^ Couldn’t resolve ‘x MyDriver’

B- try to reload
0: kd> .reload MyDriver

“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 …

C- reload with .sys

0: kd> .reload MyDriver.sys
DBGHELP: MyDriver - private symbols & lines
c:\pdb\xxx\MyDriver.pdb

D- examine : succeeds
0: kd> x MyDriver!
fffff88006838108 MyDriver!__security_cookie_complement = 0xffff077ff97c9f3e
fffff880`06838198 MyDriver!My_HS_Configuration = struct _MY_CONFIGURATION


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

On Debugger PC, I have
_NT_SYMBOL_PATH=SRV
C:\PDB\MSFT*http://msdl.microsoft.com/download/symbols;C:\PDB\XXX

After a rebuild of the driver I copy the MyDriver.pdb to C:\PDB\XXX</image.ext>

You could run ‘.reload -f -n.’

Good luck,

mm

-----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 …

A- examine : fails
kd> x MyDriver!*
^ Couldn’t resolve ‘x MyDriver’

B- try to reload
0: kd> .reload MyDriver

“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 …

C- reload with .sys

0: kd> .reload MyDriver.sys
DBGHELP: MyDriver - private symbols & lines
c:\pdb\xxx\MyDriver.pdb

D- examine : succeeds
0: kd> x MyDriver!
fffff88006838108 MyDriver!__security_cookie_complement =<br>0xffff077ff97c9f3e
fffff880`06838198 MyDriver!My_HS_Configuration = struct _MY_CONFIGURATION


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

On Debugger PC, I have
_NT_SYMBOL_PATH=SRV
C:\PDB\MSFT*http://msdl.microsoft.com/download/symbols;C
:\PDB\XXX

After a rebuild of the driver I copy the MyDriver.pdb to C:\PDB\XXX


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer</image.ext>