Trouble displaying C# stack trace in WinDbg

Question

I have a handle leak in a C# program. I'm trying to diagnose it using WinDbg using !htrace, roughly as presented in this answer, but when I run !htrace -diff in WinDbg I'm presented with stack traces that don't show the names of my C# functions (or even my .net assembly). I created a small test program to illustrate my difficulty. This program does nothing except "leak" handles. ``` class Program { static List handles = new List(); static void Main(string[] args) { while (true) { Fun1(); Thread.Sleep(100); } } static void Fun1() { handles.Add(new Semaphore(0, 10)); } } ``` I compiled the assembly, and then in WinDbg I go "File" -> "Open Executable" and select my program (D:\Projects\Sandpit\bin\Debug\Sandpit.exe). I continue program execution, break it, and run "!htrace -enable", then continue for a bit longer, and then break and run "!htrace -diff". This is what I get: ``` 0:004> !htrace -enable Handle tracing enabled. Handle tracing information snapshot success…

Accepted Answer

WinDbg attempts to interpret the native call stack as best it can, however to fully interpret the stack of a CLR application WinDbg needs to use an extension called SOS. This extension has a separate command `CLRStack` for viewing the stack information of CLR stacks. You will need to load the SOS extension first however using the `.loadby sos clr` command (or similar, I remember getting the correct version SOS to load could be a bit of a pain)

For more information see

- WinDbg 101–A step by step guide to finding a simple memory leak in your .Net application

- WinDbg / SOS Cheat Sheet

Trouble displaying C# stack trace in WinDbg

Solution

Problem

Related problems