Not finding symbols

Hello,
I recently updated to the new WinDBG build (6.9). Unfortunately WinDBG is not able to find the websymbols any more.

I deleted all workspaces from the registry, unistalled the old windbg, installed the new one, set the environment variables _NT_SYMBOL_PATH and NT_SYMBOL_PATH to ‘SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols’ (without the ').
WinDBG does recognize the symbol path. Unfortunately it is not able to find the right symbols.

What’s wrong?

Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \.\pipe\XPX86
Waiting to reconnect…
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established. (Initial Breakpoint requested)
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Wed May 7 14:34:05.437 2008 (GMT+2)
System Uptime: 0 days 0:08:28.015

kd> .reload
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols

Loading User Symbols

Loading unloaded module list

kd> dt nt!_DEVICE_OBJECT
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_DEVICE_OBJECT ***
*** ***
*************************************************************************
Symbol nt!_DEVICE_OBJECT not found.

> Hello,

I recently updated to the new WinDBG build (6.9).
Unfortunately WinDBG is not able to find the websymbols any more.

I deleted all workspaces from the registry, unistalled the
old windbg, installed the new one, set the environment
variables _NT_SYMBOL_PATH and NT_SYMBOL_PATH to
‘SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
(without the ').
WinDBG does recognize the symbol path. Unfortunately it is
not able to find the right symbols.

What’s wrong?

Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \.\pipe\XPX86
Waiting to reconnect…
Connected to Windows XP 2600 x86 compatible target, ptr64
FALSE Kernel Debugger connection established. (Initial
Breakpoint requested) Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Built by:
2600.xpsp.080413-2111 Kernel base = 0x804d7000
PsLoadedModuleList = 0x80553fc0 Debug session time: Wed May
7 14:34:05.437 2008 (GMT+2) System Uptime: 0 days 0:08:28.015

Looks like you also recently upgraded to XP Service Pack 3, like me. It
seems the SP3 symbols have not arrived at the symbol server yet :frowning:

Tim Green
Development Engineer
DisplayLink (UK) Limited

While types go missing from the symbols all the time, it does seem very unlikely that _DEVICE_OBJECT would be one of them,
especially in such an old build of the OS. That being said, everything you did looks correct, and I can’t see how the new build of
WinDbg could screw up something this fundamental and get out the door. So, in a nutshell, I really don’t know what the problem is,
but here’s what I would try.

  1. I’m sure that this isn’t it, but have you tried ‘srv’ instead of ‘SRV?’ Also, how about setting it directly with ‘.sympath.’
    What you’re doing clearly should work, but I would give it a try, as it won’t take long.

  2. I would try the following and see what it says:

.symopt+ 0x80000000
.reload -f -n
lml

Wait a minute - I just noticed that this is for SP3. Accordingly, I take back what I said about _DEVICE_OBJECT; it’s well within
the range of possibility that a symbol like this could be missing from http://msdl.microsoft.com/download/symbols. I would still
try (2) and see what it says.

Good luck,

mm

xxxxx@vansoftcorp.com wrote:

Hello,
I recently updated to the new WinDBG build (6.9). Unfortunately WinDBG is not able to find the websymbols any more.

I deleted all workspaces from the registry, unistalled the old windbg, installed the new one, set the environment variables _NT_SYMBOL_PATH and NT_SYMBOL_PATH to ‘SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols’ (without the ').
WinDBG does recognize the symbol path. Unfortunately it is not able to find the right symbols.

What’s wrong?

Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \.\pipe\XPX86
Waiting to reconnect…
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established. (Initial Breakpoint requested)
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Wed May 7 14:34:05.437 2008 (GMT+2)
System Uptime: 0 days 0:08:28.015

kd> .reload
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols

Loading User Symbols

Loading unloaded module list

kd> dt nt!_DEVICE_OBJECT
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_DEVICE_OBJECT ***
*** ***
*************************************************************************
Symbol nt!_DEVICE_OBJECT not found.

Ok, probably you are right. The public symbols do not exist yet.

Symbol nt!_KPRCB not found.
kd> .symopt+ 0x80000000
Symbol options are 0x80030237:
0x00000001 - SYMOPT_CASE_INSENSITIVE
0x00000002 - SYMOPT_UNDNAME
0x00000004 - SYMOPT_DEFERRED_LOADS
0x00000010 - SYMOPT_LOAD_LINES
0x00000020 - SYMOPT_OMAP_FIND_NEAREST
0x00000200 - SYMOPT_FAIL_CRITICAL_ERRORS
0x00010000 - SYMOPT_AUTO_PUBLICS
0x00020000 - SYMOPT_NO_IMAGE_SEARCH
0x80000000 - SYMOPT_DEBUG
kd> .reload -f -n
SYMSRV: c:\websymbols\ntoskrnl.exe\4802516A1f8f00\ntoskrnl.exe not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntoskrnl.exe/4802516A1f8f00/ntoskrnl.exe not found
SYMSRV: c:\websymbols\ntkrnlup.exe\4802516A1f8f00\ntkrnlup.exe not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntkrnlup.exe/4802516A1f8f00/ntkrnlup.exe not found
SYMSRV: c:\websymbols\ntkrnlpa.exe\4802516A1f8f00\ntkrnlpa.exe not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntkrnlpa.exe/4802516A1f8f00/ntkrnlpa.exe not found
SYMSRV: c:\websymbols\ntkrnlmp.exe\4802516A1f8f00\ntkrnlmp.exe not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntkrnlmp.exe/4802516A1f8f00/ntkrnlmp.exe not found
SYMSRV: c:\websymbols\ntkrpamp.exe\4802516A1f8f00\ntkrpamp.exe not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/4802516A1f8f00/ntkrpamp.exe not found
DBGENG: ntoskrnl.exe - Image mapping disallowed by non-local path.
Unable to load image ntoskrnl.exe, Win32 error 0n2

Hopefully the will materialize soon. Have you checked the symbols download page? Someone (I’m pretty sure it was Pavel) referred
me to this page one time a while back when I was looking for symbols for something else, and they’re were indeed there, which
surprised me, as it sure seems like less work would be involved in running symstore than changing a webpage, but whatever. In any
case, I don’t recall the URL, but there’s a link for it on the WinDbg home page (google ‘WinDbg,’ and the home page is the first
hit, I believe).

Good luck,

mm

xxxxx@vansoftcorp.com wrote:

Ok, probably you are right. The public symbols do not exist yet.

Symbol nt!_KPRCB not found.
kd> .symopt+ 0x80000000
Symbol options are 0x80030237:
0x00000001 - SYMOPT_CASE_INSENSITIVE
0x00000002 - SYMOPT_UNDNAME
0x00000004 - SYMOPT_DEFERRED_LOADS
0x00000010 - SYMOPT_LOAD_LINES
0x00000020 - SYMOPT_OMAP_FIND_NEAREST
0x00000200 - SYMOPT_FAIL_CRITICAL_ERRORS
0x00010000 - SYMOPT_AUTO_PUBLICS
0x00020000 - SYMOPT_NO_IMAGE_SEARCH
0x80000000 - SYMOPT_DEBUG
kd> .reload -f -n
SYMSRV: c:\websymbols\ntoskrnl.exe\4802516A1f8f00\ntoskrnl.exe not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntoskrnl.exe/4802516A1f8f00/ntoskrnl.exe not found
SYMSRV: c:\websymbols\ntkrnlup.exe\4802516A1f8f00\ntkrnlup.exe not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntkrnlup.exe/4802516A1f8f00/ntkrnlup.exe not found
SYMSRV: c:\websymbols\ntkrnlpa.exe\4802516A1f8f00\ntkrnlpa.exe not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntkrnlpa.exe/4802516A1f8f00/ntkrnlpa.exe not found
SYMSRV: c:\websymbols\ntkrnlmp.exe\4802516A1f8f00\ntkrnlmp.exe not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntkrnlmp.exe/4802516A1f8f00/ntkrnlmp.exe not found
SYMSRV: c:\websymbols\ntkrpamp.exe\4802516A1f8f00\ntkrpamp.exe not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/4802516A1f8f00/ntkrpamp.exe not found
DBGENG: ntoskrnl.exe - Image mapping disallowed by non-local path.
Unable to load image ntoskrnl.exe, Win32 error 0n2