DP's CODE NOTES

Use StackDump to troubleshoot .NET apps

2017-12-14

Update! Codeplex seems to have closed, unclear at the moment if this project is maintained in other ways.

StackDump is great tool when there is a problem with a .NET app in production. Since it is just an .exe there is no installation needed. And it can be an alternative to analyze huge dump files. You use it like this:

1. Find the Process Id. Open a cmd shell


// list active .Net processes with associated PID:
C:\Programs\stackdump\Net4\X64\StackDump.exe   

//example output:
//12540 w3wp.exe

2. List threads


//list all running threads in PID 12540 with stack traces:
StackDump.exe 12540     

//same as above but will put it in a file instead:
StackDump.exe 12540 > "dump.txt"

Native threads will be empty but listed. The first line in a managed thread will indicate what this thread is hanging on the time when the stacks were taken.