[Interest] Best way to terminate threads using QWaitCondition

[Thiago Macieira]

On Saturday 21 November 2015 20:01:05 Bob Hood wrote:
> On 11/21/2015 2:26 PM, Bob Hood wrote:
> > I'll attach at debugger to the child and see if I can pinpoint the thread.
> 
> Well, my Debugging-fu under Linux is not quite as good yet as it is under
> Windows.  I cannot pin down the precise thread that might be causing this,
> or even the point in time.  However, my gut tells me that it's a race
> condition where the variables (QMutex/QWaitCondition) are being destroyed
> before the threads are terminated.

Indeed, but you need to find the thread to find out which thread is exiting 
with a locked set of primitives.

Run with QT_FATAL_WARNINGS=1 and Qt will abort the program on the first 
warning, creating a core dump.

> I'm going to try some refactoring of the threading model to see if I can
> address it that way.  This is my first use of wait conditions (although I've
> used a similar synchronization model in Python).  It's a great approach to
> thread synchronization, but it's turning out to be tricky.  :)
> 
> Thanks for the help, Thiago.  I'll get back to you if I can't address it
> some other way.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center