Crash Dump Analysis

WinDbg has been updated to version 6.8.4.0

2009 (0x7D9) - The Year of Debugging

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 -

Announcements

New Books:

DLL List Landscape: The Art from Computer Memory Space

Dumps, Bugs and Debugging Forensics: The Adventures of Dr. Debugalov

WinDbg: A Reference Poster and Learning Cards

Memory Dump Analysis Anthology, Volume 2

Also available:

Memory Dump Analysis Anthology, Volume 1

New Children's Book:

Baby Turing

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.

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

Leave a Reply