Comments on: WinDbg !locks command broken http://www.voyce.com/index.php/2009/06/03/windbg-locks-command-broken/ Programming and debugging tidbits Sun, 29 Aug 2010 13:10:10 +0100 hourly 1 By: Vishwanath http://www.voyce.com/index.php/2009/06/03/windbg-locks-command-broken/comment-page-1/#comment-979 Vishwanath Thu, 12 Aug 2010 07:01:53 +0000 http://www.voyce.com/?p=163#comment-979 Thanks IAN by installing older version (6.10) i am able to see deadlocks. where as with 6.11 i couldn't. Thanks IAN by installing older version (6.10) i am able to see deadlocks. where as with 6.11 i couldn’t.

]]> By: ian http://www.voyce.com/index.php/2009/06/03/windbg-locks-command-broken/comment-page-1/#comment-850 ian Thu, 11 Mar 2010 18:33:27 +0000 http://www.voyce.com/?p=163#comment-850 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: <a href="http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx"/ rel="nofollow">http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx</a>. You need to download the ~600mb ISO, mount it and install WinDbg from the \debuggers directory. 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.

]]>