Symbol server on a 56K dialup line

WINDBG
1

Contrary to SBC, Verizon, and the others, most of this country cannot get
DSL or cable modem, requiring us to us 56K dialups.

I am having problems with the symbol server. The search path that I use
looks like this : “symsrv*symsrv.dll*D:\Symbosl*D:\Symbols\Win2k\Sys”. I
copy the PDB files for drivers to a specific platform directory in the main
Symbols cache on my local driver. I find those symbols, but WinDbg always
complains about not finding system symbols. Mostly I have not had system
symbols available for debug since I went to the 56K dialup. Anyone see
something with my search path? And naturally I have a problem where I need
the pci commands – which require valid symbols.

Here is a dump from WinDbg when I execute a pci command.

0: kd> !pcitree

*** ERROR: Module load completed but symbols could not be loaded for pci.sys

Error retrieving address of PciFdoExtensionListHead

0: kd> .reload pci.sys

0: kd> !pcitree

*** ERROR: Module load completed but symbols could not be loaded for pci.sys

Error retrieving address of PciFdoExtensionListHead

0: kd> !reload

Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrnlmp.exe -

Loading Kernel Symbols

…

Loading unloaded module list

Loading User Symbols

PEB address is NULL !

–
Gary G. Little
Have Computer, Will Travel …
909-698-3191
909-551-2105

2

What do you see when you use “!sym noisy” to see what it is actually DOING
here?

Does your local symbol directory really exist? I noticed your spelling for
it is a bit unusual in your query.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: Gary G. Little [mailto:xxxxx@inland.net]
Sent: Friday, November 29, 2002 1:30 PM
To: Kernel Debugging Interest List
Subject: [windbg] Symbol server on a 56K dialup line

Contrary to SBC, Verizon, and the others, most of this country cannot get
DSL or cable modem, requiring us to us 56K dialups.

I am having problems with the symbol server. The search path that I use
looks like this : “symsrv*symsrv.dll*D:\Symbosl*D:\Symbols\Win2k\Sys”. I
copy the PDB files for drivers to a specific platform directory in the main
Symbols cache on my local driver. I find those symbols, but WinDbg always
complains about not finding system symbols. Mostly I have not had system
symbols available for debug since I went to the 56K dialup. Anyone see
something with my search path? And naturally I have a problem where I need
the pci commands – which require valid symbols.

Here is a dump from WinDbg when I execute a pci command.

0: kd> !pcitree

*** ERROR: Module load completed but symbols could not be loaded for pci.sys

Error retrieving address of PciFdoExtensionListHead

0: kd> .reload pci.sys

0: kd> !pcitree

*** ERROR: Module load completed but symbols could not be loaded for pci.sys

Error retrieving address of PciFdoExtensionListHead

0: kd> !reload

Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrnlmp.exe -

Loading Kernel Symbols

…

Loading unloaded module list

Loading User Symbols

PEB address is NULL !

–
Gary G. Little
Have Computer, Will Travel …
909-698-3191
909-551-2105

You are currently subscribed to windbg as: xxxxx@osr.com
To unsubscribe send a blank email to %%email.unsub%%

3

“Tony Mason” wrote in message news:xxxxx@windbg…
>
> What do you see when you use “!sym noisy” to see what it is actually DOING
> here?
>
> Does your local symbol directory really exist? I noticed your spelling
for
> it is a bit unusual in your query.
>
> Regards,
>
> Tony
>
> Tony Mason
> Consulting Partner
> OSR Open Systems Resources, Inc.
> http://www.osr.com

Tony,

Good catch, but I do have it spelled right in WinDbg (yes I just checked. :slight_smile:

I enabled “!sym noisy” and did things again. !pcitree still fails. Here’s
another dump.

0: kd> !sym noisy

noisy mode - symbol prompts on

0: kd> !reload

Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE

DBGHELP: ntkrnlmp.exe is stripped. Searching for dbg file

SYMSRV: D:\Symbols\Win2K\sys\ntkrnlmp.dbg\3AD7786919b5c0\ntkrnlmp.dbg - file
not found

SYMSRV: D:\Symbols\ntkrnlmp.dbg\3AD7786919b5c0\ntkrnlmp.dbg - file not found

DBGHELP: ntkrnlmp.exe missing debug info. Searching for pdb anyway

DBGHELP: Can’t use symbol server for ntkrnlmp.pdb - no header information
available

DBGHELP: ntkrnlmp.pdb - file not found

ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrnlmp.exe -

DBGHELP: nt - export symbols

Loading Kernel Symbols

…
…

Loading unloaded module list

…

Loading User Symbols

0: kd> !pcitree

DBGHELP: pci.sys is stripped. Searching for dbg file

SYMSRV: D:\Symbols\Win2K\sys\pci.dbg\3A9EEB8Ae500\pci.dbg - file not found

SYMSRV: D:\Symbols\pci.dbg\3A9EEB8Ae500\pci.dbg - file not found

DBGHELP: pci.sys missing debug info. Searching for pdb anyway

DBGHELP: Can’t use symbol server for pci.pdb - no header information
available

DBGHELP: pci.pdb - file not found

 ERROR: Module load completed but symbols could not be loaded for pci.sys

DBGHELP: pci - no symbols loaded

Error retrieving address of PciFdoExtensionListHead

Symbol search path is: symsrvsymsrv.dllD:\SymbolsD:\Symbols\Win2K\sys

0: kd> .reload

Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE

DBGHELP: ntkrnlmp.exe is stripped. Searching for dbg file

SYMSRV: D:\Symbols\Win2K\sys\ntkrnlmp.dbg\3AD7786919b5c0\ntkrnlmp.dbg - file
not found

SYMSRV: D:\Symbols\ntkrnlmp.dbg\3AD7786919b5c0\ntkrnlmp.dbg - file not found

DBGHELP: ntkrnlmp.exe missing debug info. Searching for pdb anyway

DBGHELP: Can’t use symbol server for ntkrnlmp.pdb - no header information
available

DBGHELP: ntkrnlmp.pdb - file not found

** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrnlmp.exe -

DBGHELP: nt - export symbols

Loading Kernel Symbols

…
…

Loading unloaded module list

…

Loading User Symbols

4

Hi Gary,

You wrote with your specification following: get the symbols from the server path
D:\Symbols\Win2k\Sys and copy it to the local symbol store at D:\Symbosl (or D:\Symbols). This
construction makes no sense to me because it appeared you didn’t populated Win2K symbols over both
of these places (see the !sym noisy diagnostics, it is pretty clear). And the 56K dialup here is
irrelevant, WinDBG even not tried to get anything from the internet, because you said so. Change
your symbol search path to something like that:

D:\Path\To\PCI\Symbols;srv*D:\Symbols*http://msdl.microsoft.com/download/symbols

Good Luck,
Timur

“Gary G. Little” wrote in message
news:LYRIS-8256-86072-2002.11.29-13.29.35–timur#xxxxx@lists.osr.com…
: Contrary to SBC, Verizon, and the others, most of this country cannot get
: DSL or cable modem, requiring us to us 56K dialups.
:
: I am having problems with the symbol server. The search path that I use
: looks like this : “symsrvsymsrv.dllD:\Symbosl*D:\Symbols\Win2k\Sys”. I
: copy the PDB files for drivers to a specific platform directory in the main
: Symbols cache on my local driver. I find those symbols, but WinDbg always
: complains about not finding system symbols. Mostly I have not had system
: symbols available for debug since I went to the 56K dialup. Anyone see
: something with my search path? And naturally I have a problem where I need
: the pci commands – which require valid symbols.
:
: Here is a dump from WinDbg when I execute a pci command.
:
: 0: kd> !pcitree
:
: ERROR: Module load completed but symbols could not be loaded for pci.sys
:
: Error retrieving address of PciFdoExtensionListHead
:
: 0: kd> .reload pci.sys
:
: 0: kd> !pcitree
:
: ERROR: Module load completed but symbols could not be loaded for pci.sys
:
: Error retrieving address of PciFdoExtensionListHead
:
: 0: kd> !reload
:
: Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
:
: *** ERROR: Symbol file could not be found. Defaulted to export symbols for
: ntkrnlmp.exe -
:
: Loading Kernel Symbols
:
: …
:
: Loading unloaded module list
:
: Loading User Symbols
:
: PEB address is NULL !
:
: –
: Gary G. Little
: Have Computer, Will Travel …
: 909-698-3191
: 909-551-2105
:

5

Well I’ll bea son of a …

Timur … bless you my child. That did the trick. I have for a couple of
months now had the cart before the horse, wondering why I wasn’t smelling a
horses ass. :slight_smile:

In case anyone is interested … my new SYMPATH is:

D:\Symbols\Win2K;srv*D:\Symbols*http://msdl.microsoft.com/download/symbols

–
Gary G. Little
Have Computer, Will Travel …
909-698-3191
909-551-2105

“Timur Safin” wrote in message news:xxxxx@windbg…
>
> Hi Gary,
>
> You wrote with your specification following: get the symbols from the
server path
> D:\Symbols\Win2k\Sys and copy it to the local symbol store at D:\Symbosl
(or D:\Symbols). This
> construction makes no sense to me because it appeared you didn’t populated
Win2K symbols over both
> of these places (see the !sym noisy diagnostics, it is pretty clear). And
the 56K dialup here is
> irrelevant, WinDBG even not tried to get anything from the internet,
because you said so. Change
> your symbol search path to something like that:
>
>
D:\Path\To\PCI\Symbols;srvD:\Symbolshttp://msdl.microsoft.com/download/sym
bols
>
> Good Luck,
> Timur
>
>
> “Gary G. Little” wrote in message
>
news:LYRIS-8256-86072-2002.11.29-13.29.35–timur#xxxxx@lists.osr.com…
> : Contrary to SBC, Verizon, and the others, most of this country cannot
get
> : DSL or cable modem, requiring us to us 56K dialups.
> :
> : I am having problems with the symbol server. The search path that I use
> : looks like this : “symsrvsymsrv.dllD:\Symbosl*D:\Symbols\Win2k\Sys”. I
> : copy the PDB files for drivers to a specific platform directory in the
main
> : Symbols cache on my local driver. I find those symbols, but WinDbg
always
> : complains about not finding system symbols. Mostly I have not had system
> : symbols available for debug since I went to the 56K dialup. Anyone see
> : something with my search path? And naturally I have a problem where I
need
> : the pci commands – which require valid symbols.
> :
> : Here is a dump from WinDbg when I execute a pci command.
> :
> : 0: kd> !pcitree
> :
> : ERROR: Module load completed but symbols could not be loaded for
pci.sys
> :
> : Error retrieving address of PciFdoExtensionListHead
> :
> : 0: kd> .reload pci.sys
> :
> : 0: kd> !pcitree
> :
> : ERROR: Module load completed but symbols could not be loaded for
pci.sys
> :
> : Error retrieving address of PciFdoExtensionListHead
> :
> : 0: kd> !reload
> :
> : Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
> :
> : *** ERROR: Symbol file could not be found. Defaulted to export symbols
for
> : ntkrnlmp.exe -
> :
> : Loading Kernel Symbols
> :
> : …
> :
> : Loading unloaded module list
> :
> : Loading User Symbols
> :
> : PEB address is NULL !
> :
> : –
> : Gary G. Little
> : Have Computer, Will Travel …
> : 909-698-3191
> : 909-551-2105
> :
>
>
>
>