Home/ Questions/Q 6797667
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T18:38:13+00:00

I am using windbg to perform an analysis on a dump. Following are the

  • 0

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?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    use !clrstack –l to see local variables.

    Also look at this WinDbg / SOS Cheat Sheet

    This Blog have some great debugging guides

    • 0