All geek questions in one place

Using WinDbg to analyze .NET dump

I am using windbg to do a dump analysis. Below are the commands that I executed

  • .loadby sos mscorwks - download sos dll
  • ~* e !clrstack - view all threads
  • ~18s - changed the context to the stream I want to analyze.
  • !clrstack - see the call stack of this thread.

Now I want to go to each frame on the stack and look at the values ​​of objects / variables there. How do I proceed?

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

+4
source share
1 answer

use it! clrstack -l to see local variables.

Also look at the WinDbg / SOS Cheat Sheet

There are some great debugging guides on this blog.

+6
source

Source: https://habr.com/ru/post/1380949/

More articles:


All Articles