WinDbg tips and tricks: analyzing hangs faster
Sunday, March 4th, 2007I’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 -