Comments on: sos2.dll version 1.2 released

By: Sane

Sane — Thu, 02 Sep 2010 12:15:50 +0000

Is it possible to obtain x64 version?

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?