09-24-04 07:50 AM
Hi,
I am sorry. I wrote "analyze" instead of "!analyze" last time. When I
started over and reanalyzed again I gote following result. Something is
still wrong with the symbol path?
****************************************
************************************
***
* *
* Exception Analysis *
* *
****************************************
************************************
***
Use !analyze -v to get detailed debugging information.
****************************************
*********************************
*** ***
*** ***
*** 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. ***
*** ***
*** Type referenced: ntdll!_PEB ***
*** ***
****************************************
*********************************
Probably caused by : NTDLL.DLL ( NTDLL!KiUserExceptionDispatcher+e )
Followup: MachineOwner
---------
I found ntdll.pdb but when I point out that file I get following errror
"WARNING: C:\symbols\ntdll.pdb\4035165E1\ntdll.pdb is not accessible"
Thanks for your time!!
Zorko
"Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
news:uTY%23uNZoEHA.896@TK2MSFTNGP12.phx.gbl...
> It just means that the symbols for the dll were not located. It has
nothing
> to do with the dll's functionality, symbols are just a 'map' of the
offsets
> in the file. So, if there is a function 'foo' in the dll, the debugger
can
> give it the name 'jrun!foo' instead of jrun!+0349.
>
> The checksum is a compile time option (again, no effect on the running of
> the dll) that embeds a crc into the dll for debugging purposes.
>
> Can you post the rest of the output?
>
>
> Pat
>
> "zorko79" <zorko792002@yahoo.se> wrote in message
> news:%23HlkL1SoEHA.3792@TK2MSFTNGP11.phx.gbl...
for[vbcol=seagreen]
for[vbcol=seagreen]
for[vbcol=seagreen]
for[vbcol=seagreen]
server[vbcol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
path[vbcol=seagreen]
***[vbcol=seagreen]
to[vbcol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
may[vbcol=seagreen]
>
>
[ Post a follow-up to this message ]
|