Eric Hodel wrote:

>>>The right (wrong) sequence of locking can easily create a deadlock in
>>>the right circumstances.  I can generate a deadlock easily in Borges due
>>>to do an incorrect sequence of locks after an exception kills a thread.
>>>(The exception is only important because it allows the threads to
>>>deadlock.)
>>But isn't this considered a Ruby bug?
> No, this is definetly my bug.  If a developer can't synchronize threads
> properly, how can Ruby determine the correct way?

I just think that a developer shouldn't be able to raise the fatal 
exception which leads to deadlocks. Maybe there should be better 
checking in Thread#stop?

Regards,
Florian Gross