What is your preferred tool to track deadlocks and thread contention under .Net ?

Hi,

we're trying to find the most comfortable way to track deadlocks and thread contention in an already running .Net application (compiled as release most likely).

One way that I found out is to use perfmon (either locally or remotely) or any other tool which is able to monitor the counters in .NET CLR LocksAndThreads / Threads.

What's the best way to detect the exact line number or at least the method where a dead lock occurs (either using VS.Net, or commercial or open source tools) ?

cheers

Thibaut

[519 byte] By [ThibautBarrère] at [2007-12-16]

«« 100% cpu load ?
»» refreshing a window in mfc

# 1

Hello Thibaut,

As a member of the CLR development team, I use windbg, although there are plenty of different types of debuggers. If the deadlock is occurring in managed code and you can use cordbg, mdbg, or Visual Studio itself.

The OS debuggers (such as ntsd and windbg) include support for analyzing the time spent in threads, callstacks, and handle usage.

If you would prefer not to drop into a debugger, then perfmon/TaskMgr are certainly reasonable high-level analyzers.

Hope that helps,
Stephen
http://blogs.msdn.com/stfisher

StephenFisher-MS at 2007-9-9 >

.NET Development

.NET Base Class Library

.NET Development Hot Topic

.NET Development New Topic

.NET Development

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech