Symstore, symbols server, and windbg.

[Mike Gilson]

I'm not sure how to troubleshoot this problem, so I hope someone at
Microsoft can help out.

I have set up a symbol server and it works great for anything that I build
with the DDK (.sys, .exe, and .dll). After building my targets, I rebase
and add them to the symbol server:

rebase" -b 0x10000 -x . mydriver.sys
symstore add /r /f g:\mydrivers\*.* \\Symbols\mysymbols /t "My product"
/v "This version" /c "none"

I see the following in my symbol store:

mydriver.dbg
mydriver.pdb
mydriver.sys

Windbg can grab the symbols from the server without any problems. Same

If I try to add an app built with VS 6, no dbg is generated by the rebase.
I see the following in the symbol store:

myapp.exe
myapp.pdb

When I try to pick up the symbols with Windbg, I get the following output:

DBGHELP: No header for myapp.Exe. Searching for dbg file
DBGHELP: \\symbols\mysymbols\myapp.dbg - file not found
DBGHELP: \\symbols\mysymbols\symbols\Exe\myapp.dbg - path not found
DBGHELP: \\symbols\mysymbols\Exe\myapp.dbg - path not found
DBGHELP: myapp.Exe missing debug info. Searching for pdb anyway
DBGHELP: Can't use symbol server for myapp.pdb - no header information
available
DBGHELP: No base address for myapp.Exe: Please specify
DBGHELP: myapp- no symbols loaded
Unable to add module at 00000000

If, however, I point Windbg to a folder where myapp.exe and myapp.pdb
reside, it picks up the symbols.

So is there a way to force a search of \\symbols\mysymbols\myapp.exe and
will that cause it to match up the exe and pdb? Or do I need a dbg always?
If I always need a dbg, is this likely to be a compiler switch problem or a
problem with rebase?

Thanks,

Mike

[Andre Vachon [MS]]

.dbg files are not necessary. We have not used them in years at MS (ever
since we started working on Windows XP).

If you are trying to use a symbol server, you should set your symbol path to
srv* \\symbols\mysymbols (not just \\symbols\mysymbols)
Try that, and then show us the output from windbg.
Also, what does
lmv m mydriver*
show in the debugger ?

-Andre

Post by Mike Gilson
I'm not sure how to troubleshoot this problem, so I hope someone at
Microsoft can help out.
I have set up a symbol server and it works great for anything that I build
with the DDK (.sys, .exe, and .dll). After building my targets, I rebase
rebase" -b 0x10000 -x . mydriver.sys
symstore add /r /f g:\mydrivers\*.* \\Symbols\mysymbols /t "My product"
/v "This version" /c "none"
mydriver.dbg
mydriver.pdb
mydriver.sys
Windbg can grab the symbols from the server without any problems. Same
If I try to add an app built with VS 6, no dbg is generated by the rebase.
myapp.exe
myapp.pdb
DBGHELP: No header for myapp.Exe. Searching for dbg file
DBGHELP: \\symbols\mysymbols\myapp.dbg - file not found
DBGHELP: \\symbols\mysymbols\symbols\Exe\myapp.dbg - path not found
DBGHELP: \\symbols\mysymbols\Exe\myapp.dbg - path not found
DBGHELP: myapp.Exe missing debug info. Searching for pdb anyway
DBGHELP: Can't use symbol server for myapp.pdb - no header information
available
DBGHELP: No base address for myapp.Exe: Please specify
DBGHELP: myapp- no symbols loaded
Unable to add module at 00000000
If, however, I point Windbg to a folder where myapp.exe and myapp.pdb
reside, it picks up the symbols.
So is there a way to force a search of \\symbols\mysymbols\myapp.exe and
will that cause it to match up the exe and pdb? Or do I need a dbg always?
If I always need a dbg, is this likely to be a compiler switch problem or a
problem with rebase?
Thanks,
Mike

...