Boost Users :
Subject: Re: [Boost-users] condition_variable
From: Nikolai N Fetissov (nikolai-boost_at_[hidden])
Date: 2009-12-10 16:32:30
> Thanks Nikolai,
> That explains why the second thread can lock that mutex. From what you are
> saying then, the sleeping thread will wake up and reacquire the lock after
> notify is called. So the thread that calls notify should not hold that
> when this happens or you could have deadlock right?.
The thread calling the 'notify' can, but does not have to, hold
a mutex at the time. In theory all the notify() function does is
mark the thread sleeping on the condition as runnable. There's
no deadlock here. Also google for 'spurious wakeup' to get a firm
hold on mutex/cv concepts.
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net