« What is Memory Dump Analysis?
Crash Dumps for Dummies (Part 7) »

WinDbg has been updated to version 6.8.4.0

A bit late notice. I have just found that the new version of WinDbg was released last month:

http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx

Seems not so many enhancements in this release according to the link below and relnotes.txt and at least it is not called Beta:

http://www.microsoft.com/whdc/devtools/debugging/whatsnew.mspx

- Dmitry Vostokov @ DumpAnalysis.org -

This entry was posted on Wednesday, November 7th, 2007 at 4:32 pm and is filed under Announcements, Crash Dump Analysis, Debugging, Tools. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

3 Responses to “WinDbg has been updated to version 6.8.4.0”

  1. ClickF1 Says:
    November 8th, 2007 at 3:53 am

    Super ! Congrats !

  2. Dmitry Vostokov Says:
    November 8th, 2007 at 3:57 pm

    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
    ***
    *****************************************

  3. pawan Says:
    March 24th, 2010 at 11:07 am

    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

Leave a Reply

You must be logged in to post a comment.