RE: Aw: Re: Problems with conditions

["ross.johnson" <ross.johnson@homemail.com.au>]

That should not make any difference (unless there's a bug in the pthreads implementation). In pthreads-win32 the ERRORCHECK CV uses the ERRORCHECK mutex which adds checks to ensure the unlocking thread owns the mutex lock. (ERRORCHECK isn't meant to be used in production code btw). That it does make a difference, ie your code now works, suggests there is a dependency on timing between the threads that you need to have control of.The code that you included in your first email never sets the condition variable itself before signaling and does not check the condition variable after waking. The example shown in the link that Ger provided does both and that is the way condition variables are intended to be used. Note the example uses a while loop to check the condition variable before entering the wait and then again after waking and before unlocking the mutex. If the condition isn't true after waking the CV should go back into the wait. Google search for "condition variable spurious wakeup".Sent from my phone
-------- Original message --------From: Markus Forrer via Pthreads-win32 <pthreads-win32@sourceware.org> Date: 31/3/21  2:37 am  (GMT+10:00) To: Ger Hobbelt <ger@hobbelt.com> Cc: pthreads-win32@sourceware.org Subject: Aw: Re: Problems with conditions Thank you for your answer.The main problem was the line:pthread_mutexattr_settype(&_mutexAttribute, PTHREAD_MUTEX_ERRORCHECK); After changing to PTHREAD_MUTEX_DEFAULT it works.