Recognizing synchronization object hanging two 3rd party executables

Posted by eran on Stack Overflow See other posts from Stack Overflow or by eran
Published on 2010-05-13T07:07:54Z Indexed on 2010/05/13 7:14 UTC
Read the original article Hit count: 206

I'm using a 3rd party tool, which uses a 4th party plugin. Occasionally, the tool will hang when launched. Looking at the stack traces, I can see a few threads are waiting on WaitForSingleObject, and my bet is that they're blocking each other. Some of the threads start at the 3rt party tool, and some at the 4th party plugin.

What I'd like to do is file the most detailed complaint to the 3rd party tool vendor, assuming it's its fault (I don't trust their local support to get those details themselves). For that, I'd like to:

  1. Find out what are the synchronization objects currently waited on
  2. Find out who has created those synchronization objects

Tools currently at hand are VS2005, WinDbg and Process Explorer. OS is Window 7 64 bit. Any suggestions?

© Stack Overflow or respective owner

Related posts about debugging

Related posts about WinDbg