We have a product that uses several kernel drivers and user space
applications on NT 4.0. I think our environment lends itself well to the
Symbol Server feature of Windbg to analyze kernel dumps.
I'm trying to get the SymSrv feature working with our custom build
environment. There were some issues with how we constructed the PDB files.
Previously windbg would load the symbols only as a last resort (it would
print out a message about an "unknown sig" in verbose mode). I've had to
tinker with a couple of the complier / linker options (I can supply those if
However, it still isn't working exactly like I would think it should. For
example, I can place my PDB file in a symbol server, but I have to have the
associated SYS file in the symbol path. What I would like to do is just
have a dump and point it at the symbol server and never worry about the
binaries/symbols. Is this possible?
Does the "Reading Symbols from Paged-Out Headers" article in the Windbg help
apply to my situation at all? I have messed around with the !lmi
and !dh Windbg commands and it does appear that the debug data
directories are paged out.
Also, there is a NT registry setting called DisablePagingExecutive. I tried
that thinking that I could force the headers to remain paged-in, but it
still didn't work.
What is the relationship between the SYS file, the PDB file, and the data
contained in the dump (i.e. the header for the SYS)?
Alan Taylor CLARiiON Advanced Development, EMC? The Enterprise Storage
62 T.W. Alexander Drive, Durham, NC 27709-0023
Phone: (919) 248-6349, Tie line: 262-6349, Fax: (919) 248-5942
You are currently subscribed to windbg as: $subst('Recip.EmailAddr')
To unsubscribe send a blank email to leave-windbg-$subst('Recip.MemberIDChar')@lists.osr.com