Comments on: WinDbg has been updated to version 6.8.4.0

By: pawan

pawan — Wed, 24 Mar 2010 11:07:53 +0000

my windows debugger is showing error again and again
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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+129989 )

please tell me what should i do to exactly find the problem

By: Dmitry Vostokov

Dmitry Vostokov — Thu, 08 Nov 2007 15:57:53 +0000

Seems the new version of WinDbg generates the following messages (which can be ignored) when I open user dumps and also complete memory dumps and apply !analyze -v: 0:000> !analyze -v **************************************** * * Exception Analysis * **************************************** **************************************** *** *** 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: kernel32!pNlsUserInfo *** **************************************** **************************************** *** *** 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: kernel32!pNlsUserInfo *** *****************************************

By: ClickF1

ClickF1 — Thu, 08 Nov 2007 03:53:21 +0000

Super ! Congrats !