windbg crash dump cmd extensions

NTFSD
1

Hi Everyone,
I downloaded the latest Windbg (6.3.17), did a custom install, set my symbol
path to the following:
D:\mysymbols;SRV*D:\mssymbols*http://msdl.microsoft.com/download/symbols
and I am seeing a couple of different things.
First, in a mini-dump from a customer (hang not bsod), I type !analyze
-v and I get the banner:

*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
I don’t understand windbg complaint since I have the symbol path set to
my drivers symbols first and the Microsoft symbol server second.

Second, Microsoft has viewed this dump initially, and they use a command
!critlist which is very nice for displaying threads waiting on resources
and therefore showing deadlocks, but I cannot find critlist anywhere.

It would be very helpful to have critlist. Does anyone know where I can
get this extension?
Thanks in advance.
duane

2

For some reason it did not download the symbols. In case of a panic, my experience is that it goes out to get the symbols…

try to make the symbol down load verbose by issuing -

!sym noisy

then make sure you do

reload or .reload

You will see it down loads krnl and usr module pdbs’ , takes a bit.

Also hope you did not download beta version of windbg itself !!!

-pro

3

Also I forgot to mention, that mini-dump is really good if you debug on the failed machine or you will have to have the same os version/level installed, symbs installed before you go for debug !!!

It is much easier to get at least the kernel mode dump from user(s), if possible, and look at the place where your windbg is installed, usually there is folders for different KD extensions, and lastly dont be surprised, if the one you are using does not have the extensions you looking for, first because they chanages, second because they may never came to general distributions !

-pro