It seems that the extremely useful !locks command is broken in 6.11.1.40x, the current and previous release of WinDbg from the debugging tools for Windows.
You’ll get errors like:
0:007> !locks NTSDEXTS: Unable to resolve ntdll!RTL_CRITICAL_SECTION_DEBUG type NTSDEXTS: Please check your symbols
The suggested solution seems to be to roll-back to version 6.10.3.233, available from here, or you can just replace the version of ntsdexts.dll in the c:\program files\debugging tools for windows (x86)\winxp directory with the one from the earlier release.
Judging by the error message, I’m guessing that the new version may work if you happen to be using a debug (checked) build of the Windows kernel, but I don’t have one around to try it with.
2 Comments
Yay! The new version of WinDbg: 6.12.2.633 fixes the problem.
The bad news? It’s only available as part of the Windows Driver development kit (the WDK). You can download it from here: http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx. You need to download the ~600mb ISO, mount it and install WinDbg from the \debuggers directory.
Thanks IAN by installing older version (6.10) i am able to see deadlocks. where as with 6.11 i couldn’t.