Thread dump in .NET a la Java kill -3 PID RRS feed

  • Question

  • Hi, I am searching for a non-intrusive, lightweight .NET mechanism to get thread and monitor information.

    Java has an incredibly lightweight and powerful mechanism to help in determining JVM state, hung threads, thread pool usage called the thread dump. If you send a process the signal 3, it creates a file called javacore.txt which lists all threads, their stacks, as well as all monitors, who owns them and who is waiting to enter. The file is a small text file and takes usually less than 2 seconds to gather. It has no impact on a running JVM.

    Is there such a mechanism in .NET. Using windbg to find a process, attach to it, and then execute !threads is complex and I wonder about how intrusive it is to the runtime (especially in production). What are the options here? This is the most basic of problem determination tools and should be easily acquired.

    Friday, February 8, 2008 1:05 AM

All replies