As you can see from the output of your ‘x’ command, this is a case where
the binary is needed, and the debugger is trying to locate it from your
symbol server. My guess is that this is caused by a paged-out image
header.
I recommend having the dev team post both binary files and symbol files
to your internal symbol server. But for this specific case, check out
the debugger.chm documentation, in an article titled “Reading Symbols
from Paged-Out Headers”.
Jason
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Takin
Nili-Esfahani
Sent: Monday, April 11, 2005 5:38 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Clarification needed on SYMSRV behavior
What do you mean, ‘get errors when only the pdb is there’? What kind
of
errors are you getting? What are you trying to accomplish?
Our development team is only posting PDB files to the symbol server and
I am
trying to conduct live debugging using those symbols. I need to know
the
reason why the driver image is needed. I posted the WinDbg output
below:
kd> !sym noisy
noisy mode - symbol prompts on
kd> .reload xyz.sys
kd> x xyz!DriverEntry
SYMSRV: D:\websymbols\XYZ.SYS\42531ADA3fb40\XYZ.SYS not found
SYMSRV: http://symbolserver/unreleased/XYZ.SYS/42531ADA3fb40/XYZ.SYS
not
found
The driver starts automatically so the image is loaded in the kernel
when I
run these commands.
Takin
“Jason Shay” wrote in message
news:xxxxx@windbg…
Most of the time, the binary file is not needed. It can vary based on
if the image header is paged out.
In order to use symsrv.dll to retrieve pdb files, information from the
image header is needed. In minidump files, this is never in the dump,
so symsrv first downloads the binary file using identifying information
from the module list. Once it gets the binary, it looks in the header
for the necessary info to get the .pdb.
In live sessions, the information is usually there, but may be paged
out, which would cause a binary to be downloaded in order to retrieve
the symbol file.
What do you mean, ‘get errors when only the pdb is there’? What kind of
errors are you getting? What are you trying to accomplish?
Jason
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Takin
Nili-Esfahani
Sent: Saturday, April 09, 2005 4:02 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Clarification needed on SYMSRV behavior
So if I am doing live debugging, the binary file is not needed? Based
on my
experience with 6.4.7.0, this is not the case. The binaries are copied
into
my download stream when they are on the symbol server and I get errors
when
only the PDB is there.
Takin
“Jason Shay” wrote in message
news:xxxxx@windbg…
In general, debugging minidumps are when the binary files are needed.
Jason
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Takin
Nili-Esfahani
Sent: Saturday, April 09, 2005 1:05 PM
To: Kernel Debugging Interest List
Subject: [windbg] Clarification needed on SYMSRV behavior
I have configured WinDbg to use both the Microsoft and our internal
symbol
server.
When I look in the download stream, some modules have a PDB directory
only,
while others have both a PDB and SYS directory. In what situations does
SYMSRV download just the PDB and when does it download the PDB and the
SYS?
From the point of view of the people who maintain a symbol server, are
you
required to post both the PDB and SYS files or are there situations when
you
only post the PDB files?
—
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: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com