Thread: mutex problem

Originally Posted by grumpy

For example, if that startup code creates a file that is needed in the main thread, the main thread needs to grab the mutex, check if the file exists, and - if it doesn't - release the mutex and try again (preferably with a small Sleep() to stop thrashing the CPU).

Main thread could just create Event
and start waiting on this event

when child thread does its work it sets the event
and main thread exits the wait and starts reading file or something. no need in polling in this case

in the OP code main thread could start waiting on the mutex which is not created yet

Originally Posted by vart

Main thread could just create Event
and start waiting on this event

when child thread does its work it sets the event
and main thread exits the wait and starts reading file or something. no need in polling in this case

in the OP code main thread could start waiting on the mutex which is not created yet

Yeah, indeed. There are all sorts of ways.

The basic concern, however, is that radeberger is relying on one thread completing some action before another thread grabs the mutex. But doing nothing that ensures that sequence of events actually occurs. These things don't happen by magic.