Symbols management

WINDBG
1

Hello,

I have one very annoying problem with WinDbg.
Time to time when I stop at [embedded] breakpoint my WinDbg begins
reload symbols. Part of them is located in Microsoft, part on my
server. But there are few drivers for which symbols do not exist and
WinDbg tries to find them, shoing next listing:

*** ERROR: Module load completed but symbols could not be loaded for pfc.sys
*** ERROR: Module load completed but symbols could not be loaded for InCDPass.sys
*** ERROR: Module load completed but symbols could not be loaded for slntamr.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for SlWdmSup.sys -
*** ERROR: Module load completed but symbols could not be loaded for Mtlmnt5.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for drmk.sys -
*** ERROR: Module load completed but symbols could not be loaded for ALCXWDM.SYS
*** ERROR: Module load completed but symbols could not be loaded for ALCXSENS.SYS
*** ERROR: Module load completed but symbols could not be loaded for sisnic.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for o2mmb.sys -
*** ERROR: Module load completed but symbols could not be loaded for MbxStby.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8180.SYS
*** ERROR: Module load completed but symbols could not be loaded for InCDrec.SYS
*** ERROR: Module load completed but symbols could not be loaded for InCDfs.SYS
*** WARNING: Unable to verify timestamp for ati2dvag.dll
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll

This process is very long up to 10 minutes and quite annoying.

How can I reduce bad effects of such behaviour?

  • may be I could forbid to load some symbols?
  • may be I should disable loading symbols from the MS?
  • may be?

Thank you!

–
Best regards,
Sergey mailto:kipnis@wp.pl

2

This is caused by something which triggers a full symbol search. Some
things which are common culprits are breakpoints which aren’t defined
with a module qualifier (module!func). Another one is a watch window
variable which isn’t qualified with a module name.

There is a symbol exclusion list which you can use. This is a new
feature, but I’m pretty sure it made it into the 6.4.4 beta. You can
create a symsrv.ini file in the same location as your symsrv.dll, and
put this section in the file:
[exclusions]
No_symbols.pdb
Never_have_these.*

Jason Shay [MS]

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Sergey Kipnis
Sent: Tuesday, December 07, 2004 6:13 AM
To: Kernel Debugging Interest List
Subject: [windbg] Symbols management

Hello,

I have one very annoying problem with WinDbg.
Time to time when I stop at [embedded] breakpoint my WinDbg begins
reload symbols. Part of them is located in Microsoft, part on my
server. But there are few drivers for which symbols do not exist and
WinDbg tries to find them, shoing next listing:

*** ERROR: Module load completed but symbols could not be loaded for
pfc.sys
*** ERROR: Module load completed but symbols could not be loaded for
InCDPass.sys
*** ERROR: Module load completed but symbols could not be loaded for
slntamr.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for SlWdmSup.sys -
*** ERROR: Module load completed but symbols could not be loaded for
Mtlmnt5.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for drmk.sys -
*** ERROR: Module load completed but symbols could not be loaded for
ALCXWDM.SYS
*** ERROR: Module load completed but symbols could not be loaded for
ALCXSENS.SYS
*** ERROR: Module load completed but symbols could not be loaded for
sisnic.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for o2mmb.sys -
*** ERROR: Module load completed but symbols could not be loaded for
MbxStby.sys
*** ERROR: Module load completed but symbols could not be loaded for
RTL8180.SYS
*** ERROR: Module load completed but symbols could not be loaded for
InCDrec.SYS
*** ERROR: Module load completed but symbols could not be loaded for
InCDfs.SYS
*** WARNING: Unable to verify timestamp for ati2dvag.dll
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for
ati3duag.dll

This process is very long up to 10 minutes and quite annoying.

How can I reduce bad effects of such behaviour?

  • may be I could forbid to load some symbols?
  • may be I should disable loading symbols from the MS?
  • may be?

Thank you!

–
Best regards,
Sergey mailto:kipnis@wp.pl

You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

Another possibility is that lazy symbol loading is turned off…

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jason Shay
Sent: Tuesday, December 07, 2004 2:14 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Symbols management

This is caused by something which triggers a full symbol search. Some
things which are common culprits are breakpoints which aren’t defined
with a module qualifier (module!func). Another one is a watch window
variable which isn’t qualified with a module name.

There is a symbol exclusion list which you can use. This is a new
feature, but I’m pretty sure it made it into the 6.4.4 beta. You can
create a symsrv.ini file in the same location as your symsrv.dll, and
put this section in the file:
[exclusions]
No_symbols.pdb
Never_have_these.*

Jason Shay [MS]

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Sergey Kipnis
Sent: Tuesday, December 07, 2004 6:13 AM
To: Kernel Debugging Interest List
Subject: [windbg] Symbols management

Hello,

I have one very annoying problem with WinDbg.
Time to time when I stop at [embedded] breakpoint my WinDbg begins
reload symbols. Part of them is located in Microsoft, part on my
server. But there are few drivers for which symbols do not exist and
WinDbg tries to find them, shoing next listing:

*** ERROR: Module load completed but symbols could not be loaded for
pfc.sys
*** ERROR: Module load completed but symbols could not be loaded for
InCDPass.sys
*** ERROR: Module load completed but symbols could not be loaded for
slntamr.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for SlWdmSup.sys -
*** ERROR: Module load completed but symbols could not be loaded for
Mtlmnt5.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for drmk.sys -
*** ERROR: Module load completed but symbols could not be loaded for
ALCXWDM.SYS
*** ERROR: Module load completed but symbols could not be loaded for
ALCXSENS.SYS
*** ERROR: Module load completed but symbols could not be loaded for
sisnic.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for o2mmb.sys -
*** ERROR: Module load completed but symbols could not be loaded for
MbxStby.sys
*** ERROR: Module load completed but symbols could not be loaded for
RTL8180.SYS
*** ERROR: Module load completed but symbols could not be loaded for
InCDrec.SYS
*** ERROR: Module load completed but symbols could not be loaded for
InCDfs.SYS
*** WARNING: Unable to verify timestamp for ati2dvag.dll
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for
ati3duag.dll

This process is very long up to 10 minutes and quite annoying.

How can I reduce bad effects of such behaviour?

  • may be I could forbid to load some symbols?
  • may be I should disable loading symbols from the MS?
  • may be?

Thank you!

–
Best regards,
Sergey mailto:kipnis@wp.pl

You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com