Full Dumps are opened very slowly

WINDBG
1

Hi, guys

I am analyzing full dumps (4GB) and sometimes it takes WinDbg about 30 minutes to respond to !analyze -v…

Do you happen to know what might be the problem?
My CPU is not loaded, my machine has 4GB ram… really strange.

Thanks,
Dmitry

2

Are you getting a lot of symbol errors? Is your sympath pointing to the Microsoft symbol server?

Gary G. Little

----- Original Message -----
From: xxxxx@gmail.com
To: “Kernel Debugging Interest List”
Sent: Monday, March 21, 2011 8:24:46 AM
Subject: [windbg] Full Dumps are opened very slowly

Hi, guys

I am analyzing full dumps (4GB) and sometimes it takes WinDbg about 30 minutes to respond to !analyze -v…

Do you happen to know what might be the problem?
My CPU is not loaded, my machine has 4GB ram… really strange.

Thanks,
Dmitry

—
WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

3

I don’t get any symbol errors at all besides for two drivers on a crashing thread (our drivers).

2: kd> .sympath
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;

Strange…

4

WinDbg.exe hosts 7 threads, 6 look rather idle but one of them consumes 25% of the CPU:

ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x7d2
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PsIsSystemProcess+0x94
ntoskrnl.exe!KeStackAttachProcess+0x11c1
ntoskrnl.exe!ObReferenceObjectByPointerWithTag+0x233
msvcrt.dll!lock+0x49
msvcrt.dll!towlower_l+0x1d
dbghelp.dll!MiniDumpReadDumpStream+0x3dfeb
dbghelp.dll!MiniDumpReadDumpStream+0x3e23c
dbghelp.dll!MiniDumpReadDumpStream+0x3e40e
dbghelp.dll!MiniDumpReadDumpStream+0x3e971
dbghelp.dll!MiniDumpReadDumpStream+0x3eb78
dbghelp.dll!MiniDumpReadDumpStream+0x3e7a7
dbghelp.dll!MiniDumpReadDumpStream+0x84bc5
dbghelp.dll!MiniDumpReadDumpStream+0x65e5c
dbghelp.dll+0x2bec8
dbghelp.dll+0x2c18b
dbghelp.dll!ImagehlpApiVersionEx+0xde11
dbghelp.dll!ImagehlpApiVersionEx+0x94c6
dbghelp.dll!SymGetFileLineOffsets64+0x6d18
dbghelp.dll!SymEnumerateModulesW64+0x1d2
dbghelp.dll!SymEnumSymbolsW+0x76
dbgeng.dll!DebugCreate+0x19d1b0
dbgeng.dll!DebugCreate+0x19d75e
dbgeng.dll!DebugCreate+0x1d5cc
dbgeng.dll!DebugCreate+0x10997
dbgeng.dll!DebugCreate+0xf622b
dbgeng.dll!DebugCreate+0x10728f
dbgeng.dll!DebugCreate+0x107391
dbgeng.dll!DebugCreate+0x2626c
dbgeng.dll!DebugCreate+0x26a42
ext.dll!analyze+0x15c06
ext.dll!analyze+0x1d372
ext.dll!analyze+0x356cc
ext.dll!analyze+0x35e13
ext.dll!analyze+0x360fb
ext.dll!analyze+0x378
dbgeng.dll!DebugCreate+0xa4e42
dbgeng.dll!DebugCreate+0xa50cb
dbgeng.dll!DebugCreate+0xa51b4
dbgeng.dll!DebugCreate+0xf71fa
dbgeng.dll!DebugCreate+0x8bc4c
dbgeng.dll!DebugCreate+0xbc1c
dbgeng.dll!DebugCreate+0xbd7e
windbg.exe+0x36aba
kernel32.dll!BaseThreadInitThunk+0xd
ntdll.dll!RtlUserThreadStart+0x21

5

Do you have any un-reachable destinations in any of your path lists that will cause network timeouts for every symbol?

Larry C