How to identify deadlock conditions in a third-party application?

Posted by Imhotep is Invisible on Stack Overflow See other posts from Stack Overflow or by Imhotep is Invisible
Published on 2010-05-03T16:05:22Z Indexed on 2010/05/03 16:08 UTC
Read the original article Hit count: 175

I am using a third-party application to handle batch CD audio extraction via multiple FireWire attached devices, but the application frequently (though non-deterministically) hangs during the extraction. I suspect that the multithreaded application is deadlocking over some shared resource. The developer, however, suspects the problem lies elsewhere but is not addressing the problem at this time. I would like to be able to do some legwork on my end to a) prove the condition exists and b) ideally point him in the right direction.

The problems: while I used to be a programmer, it's been awhile and I need to shake off the dust (last work I did was back in '99 and it was under Solaris, while the application runs under XP). Rather than there being a dearth of information online, there's almost too much to digest. Are there any suggested guides or tutorials that might help me get back up to speed sufficient enough to help identify and/or diagnose the deadlock, or are there tools or approaches that I should study up on to aid me in my task?

Many thanks for all suggestions!

© Stack Overflow or respective owner

Related posts about multithreading

Related posts about Windows