On Fri, 2006-06-09 at 15:52, Jonathan Adams wrote:
> If I remember correctly, the main problems you can run into with signaling
> after dropping the lock is that there can be destruction races:
>
> thread 1Thread 2
>
> mutex_exit(&obj->mutex)
>
On Thu, 2006-06-08 at 06:48, Roch wrote:
> Quick background check: Is the thread calling cv_signal()
> holding the lock passed to cv_wait ? Normally it should.
So, for what it's worth, I've seen a lot of people confused about why
this is necessary or even helpful.
IIRC the main reason for this wa
