Recently I downloaded symbols for Windows XP sp3 and installed it in c:\Windows\symbols
and set the path in “symbol file path” in WinDbg and start the “Kernel debug” for local machine it shows that it is unable to find symbol file.
Can you tell me what exactly the problem was?
On 28 October 2010 10:44, wrote:
> Recently I downloaded symbols for Windows XP sp3 and installed it in c:\Windows\symbols
> and set the path in “symbol file path” in WinDbg and start the “Kernel debug” for local machine it shows that it is unable to find symbol file.
> Can you tell me what exactly the problem was?
>
Try running:
!sym noisy
then .reload - this should give you a better idea of the how/what/why
of the issue.
–
AdamT
Puns: The leading cause of Lojban advocacy.
I did as you said. Here What I have got
DBGHELP: c:\windows\symbols\ntdll.pdb - file not found
DBGHELP: c:\windows\symbols\dll\ntdll.pdb - mismatched pdb
DBGHELP: c:\windows\symbols\symbols\dll\ntdll.pdb - file not found
DBGHELP: ntdll.pdb - file not found
DBGHELP: Couldn’t load mismatched pdb for C:\WINDOWS\system32\ntdll.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll -
DBGHELP: ntdll - export symbols
What does it mean by mismatched pdb?I am using sp3 symbols and current os is also sp3.
On 28 October 2010 11:37, wrote:
> I did as you said. Here What I have got
> DBGHELP: c:\windows\symbols\ntdll.pdb - file not found
> DBGHELP: c:\windows\symbols\dll\ntdll.pdb - mismatched pdb
> DBGHELP: c:\windows\symbols\symbols\dll\ntdll.pdb - file not found
> DBGHELP: ntdll.pdb - file not found
> DBGHELP: Couldn’t load mismatched pdb for C:\WINDOWS\system32\ntdll.dll
> *** ERROR: Symbol file could not be found. ?Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll -
> DBGHELP: ntdll - export symbols
>
Hmm… I have a \symbols\ntdll.pdb directory, although I’m using the
public symbol server, not a downloaded symbol pack.
> What does it mean by mismatched pdb?I am using sp3 symbols and current os is also sp3.
>
It’s possible that you have installed another patch/hotfix which has
changed the version of ntdll.dll, beyond the version found in the
normal vanilla SP3 install. If this is a fresh install, check which
hotfixes you’re slip-streaming into the build.
–
AdamT
Puns: The leading cause of Lojban advocacy.
It sounds like you have the wrong symbols. Is there some reason why you
can’t use the msft symbol server (like maybe lack of internet)? Unless you
absolutely cannot use it, I would strongly recommend using it, as it
prevents problems like this from occurring for the most part, and in some
cases - perhaps yours - downloaded symbol packages just aren’t going to be
correct due to hotfixes/et. c.
.symopt+ 0x80000000
.sympath srv**http://msdl.microsoft.com/download/symbols
.reload -f *
lme
The output of ‘lme’ should largely consist of entries that say that they are
using public pdb symbols.
Good luck,
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Adam Thompson
Sent: Thursday, October 28, 2010 6:48 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Problem Connecting to symbol file path
On 28 October 2010 11:37, wrote:
> I did as you said. Here What I have got
> DBGHELP: c:\windows\symbols\ntdll.pdb - file not found
> DBGHELP: c:\windows\symbols\dll\ntdll.pdb - mismatched pdb
> DBGHELP: c:\windows\symbols\symbols\dll\ntdll.pdb - file not found
> DBGHELP: ntdll.pdb - file not found
> DBGHELP: Couldn’t load mismatched pdb for C:\WINDOWS\system32\ntdll.dll
> *** ERROR: Symbol file could not be found. ?Defaulted to export symbols
for C:\WINDOWS\system32\ntdll.dll -
> DBGHELP: ntdll - export symbols
>
Hmm… I have a \symbols\ntdll.pdb directory, although I’m using the
public symbol server, not a downloaded symbol pack.
> What does it mean by mismatched pdb?I am using sp3 symbols and current os
is also sp3.
>
It’s possible that you have installed another patch/hotfix which has
changed the version of ntdll.dll, beyond the version found in the
normal vanilla SP3 install. If this is a fresh install, check which
hotfixes you’re slip-streaming into the build.
–
AdamT
Puns: The leading cause of Lojban advocacy.
—
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer