title: Using WinDbg to analyze .NET dump
body: <p>I am using windbg to perform an analysis on a dump. Following are the commands that I have ran</p>
  
  <ol>
  <li><code>.loadby sos mscorwks</code> - to load the sos dll  </li>
  <li><code>~* e !clrstack</code> - to look at all the threads</li>
  <li><code>~18s</code> - changed the context to the thread I want to analyze</li>
  <li><code>!clrstack</code> - to look at the call stack of this thread.</li>
  </ol>
  
  <p>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?</p>
  
  <p>Is there a way to to find out at what line number in the method the thread is actually stuck?</p>