WinDbg tips and tricks: analyzing hangs faster
I’ve just found (by using Google) that the additional parameter (-hang) to the venerable !analyze -v command is rarely used… Here is the command I use if I get a manually generated dump and there is no exception in it reported by !analyze -v and subsequent visual inspection of ~*kv output doesn’t show anything suspicious, leading to hidden exception(s):
!analyze -hang -v
Then I always double check with !locks command because there could be multiple hang conditions in a dump.
The same parameter can be used in kernel memory dumps too. But double checking ERESOURCE locks (!locks), kernel threads (!stacks) and DPC queues (!dpcs) manually is highly recommended.
- Dmitry Vostokov -
March 6th, 2007 at 2:18 pm
Are you aware of SieExtPub extension?
There are two commands I often use in such cases: !Waitlist and !Critlist
Cheers,
Volker
March 6th, 2007 at 8:04 pm
Just googled and found many references to it, for example:
http://msdn.microsoft.com/msdnmag/issues/05/07/Debugging/
I rememeber I read that article some time ago but I didn’t pay attention to !critlist because I was always analyzing critical sections manually.
Anyway I’ll check this extention and other commands from it.
Thanks,
Dmitry
May 31st, 2007 at 10:00 pm
Good and popular site!