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 thre
On 11/21/2015 2:26 PM, Bob Hood wrote:
On 11/21/2015 1:26 PM, Thiago Macieira wrote:
that are synchronizing using QMutex/QWaitCondition. In my working
code, I'm getting error messages that look like:
QWaitCondition: cv destroy failure: Device or resource busy
QWaitCondition: mutex
On 11/21/2015 1:26 PM, Thiago Macieira wrote:
that are synchronizing using QMutex/QWaitCondition. In my working
code, I'm getting error messages that look like:
QWaitCondition: cv destroy failure: Device or resource busy
QWaitCondition: mutex destroy failure: Device or resource busy
On Saturday 21 November 2015 13:12:03 Bob Hood wrote:
> I wanted some advice from the brain trust on the best means of terminating
> threads
Just to be clear: you need to exit cleanly. Do not ever use the terminate()
call.
You're not doing that. I just wanted to get this out front before anyone
I wanted some advice from the brain trust on the best means of terminating
threads that are synchronizing using QMutex/QWaitCondition. In my working
code, I'm getting error messages that look like:
QWaitCondition: cv destroy failure: Device or resource busy
QWaitCondition: mutex destro
