[Qt-interest] QMutex deadlock without using QMutex

[william.crocker at analog.com]

> 
>> My question is what are good debugging tools to get this kind of information?
>> Obviously this is platform dependent, but for the sake of argument, what tools
>> are available (and how best do you use them) on linux / gcc and/or windows / vs
>> and/or windows / mingw?
> 
> gdb will give you a backtrace of all your threads... even 
> from a core dump.
> 
>     thread apply all bt
> 
> That's what I usually use.  It helps if you have debugging 
> symbols *and* source code for your libs. Most of my 
> experience is doing this in Linux.
> 


...and if the process is frozen and you see one thread waiting
for a mutex you can surmise that one of the other threads is
currently holding it. Two threads waiting for different mutii
is just icing on the cake.

Bill