Debugging DotNet app  with Windbg + SOS Winson
Why? Crash dump analysis CLR internal Pre-requirement: download & installing WinDbg from MSDN
 
http://msdn.microsoft.com/en-us/magazine/cc163791.aspx
C:\Program Files\Debugging Tools for Windows (x86) C:\Windows\Microsoft.NET\Framework\v2.0.50727 mscordacwks.dll mscorwks.dll SOS.dll
Sample app
srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Start running target app The code has console.readkey(), so could keep in memory Using “start without debugging”
Using “Attach to running process” Don’t know why I can’t use “open executable…”. In my testing only “attach..” could load sos.
Using command “.load sos”
!sos.help !help funcname
!dumpheap
!dumpheap –type Program
!dumpobj 01359be0
Video http://channel9.msdn.com/blogs/egibson/msdn-simulcast-techniques-in-advanced-net-debugging-with-john-robbins-part-1-of-3
Links http://blogs.msdn.com/b/tess/ http://www.codeproject.com/KB/cs/net_type_internals.aspx http://blogs.msdn.com/b/dougste/archive/2008/08/08/a-big-list-of-debugging-resources.aspx http ://www.microsoft.com/download/en/details.aspx?id=21255   Psscor Managed-Code Debugging Extension for WinDbg http ://blogs.msdn.com/b/tess/archive/2010/03/01/new-commands-in-sos-for-net-4-0-part-1.aspx http://blogs.msdn.com/b/tom/

Windbg dot net_clr2