Using WinDbg to analyze .NET dump

.net windbg dump crash-dumps sos
RRR picture RRR · Nov 12, 2011 · Viewed 10.3k times · Source

I am using windbg to perform an analysis on a dump. Following are the commands that I have ran

  1. .loadby sos mscorwks - to load the sos dll
  2. ~* e !clrstack - to look at all the threads
  3. ~18s - changed the context to the thread I want to analyze
  4. !clrstack - to look at the call stack of this thread.

Now, I want to go to each frame in the stack and look at the values of the objects/variables there. How should I proceed?

Is there a way to to find out at what line number in the method the thread is actually stuck?

Answer

Asher picture Asher · Nov 12, 2011

use !clrstack –l to see local variables.

Also look at this WinDbg / SOS Cheat Sheet

This Blog have some great debugging guides

Related questions

WinDbg and SoS, how do I print/dump a large string?

I am debugging a hangdump coming from a production server using WinDbg with the SoS extension. There is a string parameter in one of the stacks, that I need to know the value of. However, it is a rather large …

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

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 …

Read More
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