I am looking inside w3wp.exe process dumps right now and I wanted to document here some interesting and important steps to get WinDbg up and running, and returning interesting results (in order)!
- set _NT_EXECUTABLE_IMAGE_PATH=SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Loading CLR debugging tools:
- .loadby sos.dll mscorwks
- .load c:\psscor2\amd64\psscor2.dll
Storing results to file:
- .logopen /d
Checking the various memory heaps:
- !dumpheap -stat
- !dumpheap -type System.String -min 10000
- !dumpheap -type System.String -max 10000
This will allow you to see the heap memory consumption, the strings that are less than 1000 bytes and then above 10000.
Very useful if you need to find out where memory is going to!