Comments on: sos2.dll version 1.2 released

By: OutOfMemoryException, Managed Debugging, .NET Debugging | Debugging tidbits

OutOfMemoryException, Managed Debugging, .NET Debugging | Debugging tidbits — Tue, 05 May 2009 05:14:05 +0000

[...] ahead and look at the managed heap stats, gc handles and the objects in finalize queue. We will use sos2.dll copied under the same folder as windbg executable, we will dump only pinned and strong gchanldes to [...]

By: Nadine

Nadine — Sun, 12 Apr 2009 00:59:24 +0000

Hello,
debuggingblog.com - da best. Keep it going!

Thank you
Nadine

By: Elcorin

Elcorin — Thu, 05 Feb 2009 04:28:00 +0000

Hello,
Not sure that this is true) but thanks

Thank you
Elcorin

By: prashant

prashant — Thu, 20 Nov 2008 04:30:23 +0000

Naryan, there has to be some issue thats why this command causes hangs for ilya's app. Ilya has provided the callstack so i will look into it more once i get to it.

Debugging rules says it aint fixed until you fix it, so i do have to fix it

By: Narayan

Narayan — Thu, 20 Nov 2008 00:14:31 +0000

Very useful to analyze dumps for memory leaks. All I can say works for me so far, however a missing column compare to sos!gchandles

By: prashant

prashant — Wed, 19 Nov 2008 11:41:33 +0000

I have not been able to recreate the same issue what Ilya is having but I did find a bug which is fixed. I will continue to use sos2 over next few days in production debugging and hopefully recreate the same issue.

Please do report a bug to me if you find any.

By: Ilya Ryzhenkov

Ilya Ryzhenkov — Wed, 19 Nov 2008 08:03:52 +0000

For me, !gcht -t p hangs with the same callstacks

By: Nesin

Nesin — Wed, 19 Nov 2008 07:41:07 +0000

Yes, thank you

Run the following command to get pinned gchandles and it works for me

!gcht -t p

I have not gone through each of the options but pinned and strong gchandles worked for me. Lucky Me

By: prashant

prashant — Tue, 18 Nov 2008 21:47:25 +0000

My Apology, I may have messed it up somewhere. Could you please let me know the type which you tried to dump or the command syntax you used? also did you run it on a memory dump or just live debugging?

By: Ilya Ryzhenkov

Ilya Ryzhenkov — Tue, 18 Nov 2008 21:44:02 +0000

Stacktraces when hung:
0:000> ~* e kb
ChildEBP RetAddr Args to Child
0006ddc8 7c90df3c 7c91b22b 000007e0 00000000 ntdll!KiFastSystemCallRet
0006ddcc 7c91b22b 000007e0 00000000 00000000 ntdll!NtWaitForSingleObject+0xc
0006de54 7c901046 002f3d40 020c97c6 022f3d40 ntdll!RtlpWaitForCriticalSection+0×132
0006de5c 020c97c6 022f3d40 0006dea8 0006de7c ntdll!RtlEnterCriticalSection+0×46
0006de84 020cd65c 2d6b3c43 0000000f 007894b8 dbgeng!ClientListCapture::Fill+0×16
0006ded0 0102af20 007871f4 007894bc 0006deec dbgeng!DebugClient::ExitDispatch+0×5c
0006dee0 01044856 0078e8f8 0006def8 0101f961 windbg!UpdateEngine+0×30
0006deec 0101f961 0078e8f8 0006df18 01022f08 windbg!StateBuffer::UiRequestRead+0×16
0006def8 01022f08 7c90120e 00000000 0006ef64 windbg!WinDisassembly::SetCurInstr+0×41
0006df18 01052a53 7c90120e 00000000 00000000 windbg!UpdateCodeDisplay+0×58
0006ff7c 010560e6 00000001 00784748 007859a8 windbg!wmain+0×333
0006ffc0 7c817067 00300035 00310033 7ffdf000 windbg!_initterm_e+0×163
0006fff0 00000000 01056217 00000000 78746341 kernel32!BaseProcessStart+0×23
ChildEBP RetAddr Args to Child
00fcff14 7c90df3c 7c8025db 000000c4 00000001 ntdll!KiFastSystemCallRet
00fcff18 7c8025db 000000c4 00000001 00000000 ntdll!NtWaitForSingleObject+0xc
00fcff7c 020cd59a 000000c4 ffffffff 00000001 kernel32!WaitForSingleObjectEx+0xa8
00fcff9c 0102acad 007894bc ffffffff 806e6ef2 dbgeng!DebugClient::DispatchCallbacks+0×4a
00fcffb4 7c80b713 00000000 7c90e900 7c910040 windbg!EngineLoop+0×30d
00fcffec 00000000 0102a9a0 00000000 00000000 kernel32!BaseThreadStart+0×37
ChildEBP RetAddr Args to Child
01fdffc8 7c950010 00000005 00000004 00000001 ntdll!DbgBreakPoint
01fdfff4 00000000 00000000 00000000 00000000 ntdll!DbgUiRemoteBreakin+0×2d

By: Ilya Ryzhenkov

Ilya Ryzhenkov — Tue, 18 Nov 2008 21:36:33 +0000

Unfortunately, it just hangs in the middle of that command Looks like it hangs when trying to output some type name, as it displays some data and when it is time to show type name - *BUSY* forever…

By: Ilya Ryzhenkov

Ilya Ryzhenkov — Tue, 18 Nov 2008 14:15:03 +0000

Thanks a lot! Firing WinDbg to try it out immediately!