What is the best way (aside from adding a metric assload of debugging output statements) to determine where and, more importantly, <I>why</I> a deadlock may be happening? This is on linux, using C++ ...

Take advantage of the Mutex class to synchronize threads in different processes and the Semaphore class to limit the number of threads that can access a shared resource. Thread synchronization is used ...