4

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?

Asher
  • 1,867
  • 15
  • 24
RRR
  • 575
  • 1
  • 11
  • 25

1 Answers1

6

use !clrstack –l to see local variables.

Also look at this WinDbg / SOS Cheat Sheet

This Blog have some great debugging guides

Asher
  • 1,867
  • 15
  • 24