!locks command won't work anymore

jetq88

unread,

Mar 26, 2009, 11:00:46 AM3/26/09

to

when use !locks command, it showed following error
0:000> !locks
NTSDEXTS: Unable to resolve ntdll!RTL_CRITICAL_SECTION_DEBUG type
NTSDEXTS: Please check your symbols

0:000> .sympath
Symbol search path is: SRV*C:\symbols\MsSymbols*http://
msdl.microsoft.com/download/symbols
Expanded Symbol search path is: srv*c:\symbols\mssymbols*http://
msdl.microsoft.com/download/symbols

windbg is 6.11.0001.402 on windows xp sp3.

more info:

0:000> version
Windows XP Version 2600 (Service Pack 3) MP (4 procs) Free x86
compatible
Product: WinNt, suite: SingleUserTS
kernel32.dll version: 5.1.2600.5512 (xpsp.080413-2111)
Machine Name:
Debug session time: Tue Feb 24 15:09:26.000 2009 (GMT-5)
System Uptime: 3 days 22:17:36.037
Process Uptime: 0 days 0:43:30.000
Kernel time: 0 days 0:00:00.000
User time: 0 days 0:00:00.000
Full memory user mini dump: C:\windbg
\Hang_Mode__Date_02-24-2009__Time_14-09-23PM
\PID-5908__ASPNET_WP.EXE__full_1750_2009-02-24_14-09-25-455_1714.dmp

command line: '"C:\windbg\windbg.exe" -c ".cmdtree c:\windbg
\clr10\cmdtree03.txt' Debugger Process 0xE8C
dbgeng: image 6.11.0001.402, built Fri Jan 30 18:03:28 2009
[path: C:\windbg\dbgeng.dll]
dbghelp: image 6.11.0001.402, built Fri Jan 30 18:03:16 2009
[path: C:\windbg\dbghelp.dll]
DIA version: 11212
Extension DLL search Path:
C:\windbg\WINXP;C:\windbg\winext;C:\windbg\winext\arcade;C:\windbg
\pri;C:\windbg;C:\windbg\winext\arcade;C:\Program Files\Nice Systems
\NICE Player Codec Pack\;C:\Reuters\Plus\;C:\rsfdata;C:\Reuters\Plus;C:
\Reuters\Plus\COMLOGIN;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:
\Program Files\Attachmate\Reflection\;c:\Program Files\Microsoft SQL
Server\90\Tools\binn\;C:\Program Files\doxygen\bin;C:\Program Files
\Graphviz2.20\Bin;C:\Program Files\Code Collaborator Client;C:\WINDOWS
\system32\WindowsPowerShell\v1.0;C:\Tools\Bin;
Extension DLL chain:
dbghelp: image 6.11.0001.402, API 6.1.6, built Fri Jan 30 18:03:16
2009
[path: C:\windbg\dbghelp.dll]
ext: image 6.11.0001.402, API 1.0.0, built Fri Jan 30 18:03:14
2009
[path: C:\windbg\winext\ext.dll]
exts: image 6.11.0001.402, API 1.0.0, built Fri Jan 30 18:03:09
2009
[path: C:\windbg\WINXP\exts.dll]
uext: image 6.11.0001.402, API 1.0.0, built Fri Jan 30 18:03:11
2009
[path: C:\windbg\winext\uext.dll]
ntsdexts: image 6.1.7015.0, API 1.0.0, built Fri Jan 30 18:02:30
2009
[path: C:\windbg\WINXP\ntsdexts.dll]

pat styles [microsoft]

unread,

Mar 26, 2009, 12:23:29 PM3/26/09

to

Do you have any symbols at all for ntdll.dll? What does this command say?

!lmi ntdll.dll

.pat styles [microsoft]

"jetq88" <jetq...@gmail.com> wrote in message
news:472a18cc-1b25-49f5...@p42g2000prp.googlegroups.com...

jkwold

unread,

Mar 26, 2009, 5:28:07 PM3/26/09

to

I'm not the original poster but just encountered the same thing,
already reverted to 6.10.3.233 to get back the function. From there
issued !lmi:

0:032> !lmi ntdll.dll
Loaded Module Info: [ntdll.dll]
Module: ntdll
Base Address: 7c900000
Image Name: ntdll.dll
Machine Type: 332 (I386)
Time Stamp: 4802a12c Sun Apr 13 19:11:24 2008
Size: af000
CheckSum: b62bc
Characteristics: 210e perf
Debug Data Dirs: Type Size VA Pointer
CODEVIEW 22, 7af94, 7a394 RSDS - GUID:
{17510032-60CA-4259-8C0F-B326585000ED}
Age: 2, Pdb: ntdll.pdb
CLSID 4, 7af90, 7a390 [Data not mapped]
Image Type: MEMORY - Image read successfully from loaded
memory.
Symbol Type: PDB - Symbols loaded successfully from symbol
server.
c:\symbols\ntdll.pdb
\1751003260CA42598C0FB326585000ED2\ntdll.pdb
Load Report: public symbols , not source indexed
c:\symbols\ntdll.pdb
\1751003260CA42598C0FB326585000ED2\ntdll.pdb

So both versions of windbg were seeing the same ntdll.pdb as fetched
at some point in the past from the symbol server.

Jon

On Mar 26, 11:23 am, "pat styles [microsoft]"
<pat.sty...@microsoft.com> wrote:
> Do you have anysymbolsat all forntdll.dll? What does this command say?
>
> !lmintdll.dll
>
> .pat styles [microsoft]
>

jkwold

unread,

Mar 26, 2009, 6:28:16 PM3/26/09

to

Perhaps better info, on 6.10.3.233:

0:027> dt ntdll!_RTL_CRIT*
ntdll!_RTL_CRITICAL_SECTION
ntdll!_RTL_CRITICAL_SECTION_DEBUG

Whereas 6.11.1.402 complained about not finding the underscore-less
ntdll!RTL_CRITICAL_SECTION_DEBUG.

Jon

pat styles [microsoft]

unread,

Mar 28, 2009, 8:25:00 PM3/28/09

to

It appears you have found a bug in the !locks extension. This will be fixed
in the next debugger release. Until then you can use the ntsdexts.dll (in
the winxp subdirectory) from th 6.10 release of the debugger as a
workaround.

.pat styles [microsoft]

"jkwold" <jkw...@excite.com> wrote in message
news:6914d775-80d3-45ec...@o11g2000yql.googlegroups.com...

fink[unisys]@discussions.microsoft.com walt fink[unisys]

unread,

Jun 17, 2009, 11:15:03 AM6/17/09

to

I'm hitting the same exact problem but don't understand how to use the
suggested workaround. Could someone please explain how to use it?

"pat styles [microsoft]" wrote:

> It appears you have found a bug in the !locks extension. This will be fixed
> in the next debugger release. Until then you can use the ntsdexts.dll (in
> the winxp subdirectory) from th 6.10 release of the debugger as a
> workaround.
>

> ..pat styles [microsoft]

jkwold

unread,

Jun 23, 2009, 1:21:52 PM6/23/09

to

I suspect one would install the older windbg, save off a copy of that
version of ntsdexts.dll as say ntsdexts_ok.dll, then upgrade again to
the most current windbg (if not already fixed there), ensure the
ntsdexts_ok.dll is placed alongside the now-updated-but-not-working-
well ntsdexts.dll, and load it as !ntsdexts_ok.locks ...

Jon

On Jun 17, 10:15 am, walt fink[unisys] <walt fink[unisys]