How to list call stack of all managed threads using WinDBG?

c# .net windbg crash-dumps
sarat picture sarat · Nov 16, 2011 · Viewed 34.4k times · Source

I have a dump created from a managed application. I am using SOS/SOSEX extentions to ease my dump analysis. I'd like to list down the call stack of all managed threads as we do ~*kb with native applications. How do we do that?

Answer

Justin picture Justin · Nov 16, 2011

Use the !EEStack command:

0:007> .load sos
0:007> !EEStack

See SOS.dll (SOS Debugging Extension)

Related questions

Large Object Heap Fragmentation

The C#/.NET application I am working on is suffering from a slow memory leak. I have used CDB with SOS to try to determine what is happening but the data does not seem to make any sense so I …

Read More
How to debug corruption in the managed heap

My program throws an error which it cannot handle by a catch(Exception e) block and then it crashes: Access Violation Corrupted State Exception. This is the weird thing, because, as I know, corrupted state exceptions are thrown from unmanaged …

Read More
WinDbg/SOS: Explanation of !SyncBlk output

I am looking of a description of the output generated by the !SyncBlk command of SOS. Particularly I found no useful explanation on the column "MonitorHeld". This column shows high values in a series of crash dumps. Example: 0:000> !SyncBlk …

Read More