Hi,
I am trying to solve a bug check and !analyze -v gives me a stack command of
cxr XXXXXXXXXXXXX <- whatever value. Now thats fine but when I try to do
that I get the following error:
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** ***
*************************************************************************
Couldn’t resolve error at ‘fffffffffe2d0528’
I used !sym noisy and found that every symbol file loaded has “public
symbols” in front of it (including my driver’s).
So where do I get any other type of symbols? I am using the MS symbols
server as well as 2600 and 3615 (from WinHEC) symbols. I am running a free
build on my test machine (could that be the problem?).
I am pretty much just starting out with WinDBG and It is giving me no end of
troubles with respect to symbols.
Any help would be appreciated,
Chris
Correction: My symbols do not say public, they’re private.
…Chris
----- Original Message -----
From: “Chris Dore”
To: “Kernel Debugging Interest List”
Sent: Thursday, May 23, 2002 9:41 AM
Subject: [windbg] Symbols
> Hi,
>
> I am trying to solve a bug check and !analyze -v gives me a stack command
of
> cxr XXXXXXXXXXXXX <- whatever value. Now thats fine but when I try to do
> that I get the following error:
>
>
>
>
> Your debugger is not using the correct symbols
>
> In order for this command to work properly, your symbol path
> must point to .pdb files that have full type information.
>
> Certain .pdb files (such as the public OS symbols) do not
> contain the required information. Contact the group that
> provided you with these symbols if you need this command to
> work.
>
>
>
> Couldn’t resolve error at ‘fffffffffe2d0528’
>
> I used !sym noisy and found that every symbol file loaded has “public
> symbols” in front of it (including my driver’s).
> So where do I get any other type of symbols? I am using the MS symbols
> server as well as 2600 and 3615 (from WinHEC) symbols. I am running a free
> build on my test machine (could that be the problem?).
>
> I am pretty much just starting out with WinDBG and It is giving me no end
of
> troubles with respect to symbols.
>
> Any help would be appreciated,
> Chris
Does it work if you drop the top 32-bits of "f"s?
i.e. typeing “.cxr fe2d0528”
The public symbol message from debugger really means that the debugger
was attempting to locate type information in the PDB and couldn’t find
any. This is not something I would expect to happen when executing a
.cxr command.
Are you possitive that you typed it correctly? The “Couldn’t resolve”
message leads me to believe you typed the command incompletely or wrong.
You should have typed “.cxr fffffffffe2d0528”, is this what you did?
-----Original Message-----
From: Chris Dore [mailto:xxxxx@connecttech.com]
Sent: Thursday, May 23, 2002 6:55 AM
To: Kernel Debugging Interest List
Subject: [windbg] Re: Symbols
Correction: My symbols do not say public, they’re private. …Chris
----- Original Message -----
From: “Chris Dore”
To: “Kernel Debugging Interest List”
Sent: Thursday, May 23, 2002 9:41 AM
Subject: [windbg] Symbols
> Hi,
>
> I am trying to solve a bug check and !analyze -v gives me a stack
> command
of
> cxr XXXXXXXXXXXXX <- whatever value. Now thats fine but when I try to
> do that I get the following error:
>
>
*
>
>
> Your debugger is not using the correct symbols
>
> In order for this command to work properly, your symbol path
> must point to .pdb files that have full type information.
>
> Certain .pdb files (such as the public OS symbols) do not
> contain the required information. Contact the group that
> provided you with these symbols if you need this command to
> work.
>
>
>
> ***
> Couldn’t resolve error at ‘fffffffffe2d0528’
>
> I used !sym noisy and found that every symbol file loaded has “public
> symbols” in front of it (including my driver’s). So where do I get any
> other type of symbols? I am using the MS symbols server as well as
> 2600 and 3615 (from WinHEC) symbols. I am running a free build on my
> test machine (could that be the problem?).
>
> I am pretty much just starting out with WinDBG and It is giving me no
> end
of
> troubles with respect to symbols.
>
> Any help would be appreciated,
> Chris
—
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%
Yup, I did it with and without the top 32-bits and I made sure I did it
exactly.
This is what is bothering me. I have had it working before, a few weeks ago,
and haven’t really changed anything, only some minor changes to the path to
my driver’s sym file (and it is correct and loaded).
It’s pretty annoying 
----- Original Message -----
From: “Nathan Nesbit”
To: “Kernel Debugging Interest List”
Sent: Thursday, May 23, 2002 1:17 PM
Subject: [windbg] Re: Symbols
Does it work if you drop the top 32-bits of "f"s?
i.e. typeing “.cxr fe2d0528”
The public symbol message from debugger really means that the debugger
was attempting to locate type information in the PDB and couldn’t find
any. This is not something I would expect to happen when executing a
cxr command.
Are you possitive that you typed it correctly? The “Couldn’t resolve”
message leads me to believe you typed the command incompletely or wrong.
You should have typed “.cxr fffffffffe2d0528”, is this what you did?
-----Original Message-----
From: Chris Dore [mailto:xxxxx@connecttech.com]
Sent: Thursday, May 23, 2002 6:55 AM
To: Kernel Debugging Interest List
Subject: [windbg] Re: Symbols
Correction: My symbols do not say public, they’re private. …Chris
----- Original Message -----
From: “Chris Dore”
To: “Kernel Debugging Interest List”
Sent: Thursday, May 23, 2002 9:41 AM
Subject: [windbg] Symbols
> Hi,
>
> I am trying to solve a bug check and !analyze -v gives me a stack
> command
of
> cxr XXXXXXXXXXXXX <- whatever value. Now thats fine but when I try to
> do that I get the following error:
>
>
*
>
>
> Your debugger is not using the correct symbols
>
> In order for this command to work properly, your symbol path
> must point to .pdb files that have full type information.
>
> Certain .pdb files (such as the public OS symbols) do not
> contain the required information. Contact the group that
> provided you with these symbols if you need this command to
> work.
>
>
>
> ***
> Couldn’t resolve error at ‘fffffffffe2d0528’
>
> I used !sym noisy and found that every symbol file loaded has “public
> symbols” in front of it (including my driver’s). So where do I get any
> other type of symbols? I am using the MS symbols server as well as
> 2600 and 3615 (from WinHEC) symbols. I am running a free build on my
> test machine (could that be the problem?).
>
> I am pretty much just starting out with WinDBG and It is giving me no
> end
of
> troubles with respect to symbols.
>
> Any help would be appreciated,
> Chris
—
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%
—
You are currently subscribed to windbg as: xxxxx@connecttech.com
To unsubscribe send a blank email to %%email.unsub%%