[hidden email] wrote:
> Earlier today, I wrote:
>> In the deadlock situation, the futex has somehow taken on the value
>> 0x80000000 (the FUTEX_WAITERS value).
> But at the bottom of the loop, the compare swap operation tries to
> acquire the lock from a 0 value. Both threads execute that
> loop and are
Ah, I see in CVS that it was fixed on May 7, in a slightly different