Re: deadlock/segmentation fault when running barriers

Sascha Hunold wrote:
> I try to run 2 different barriers for a given number of times. I use 2 
> barriers cause I want to use the simplest barrier implementation 
> possible to avoid other sources of deadlocks.
> When I run this code the Ruby interpreter reports an error from time 
> to time (it doesn't always occur). The error differs from Ruby version 
> to Ruby version and also depends on the processor architecture (x86, 
> ia64). Ruby may throw a 'deadlock error' and crashes with segmentation 
> fault.
>
>
> I would appreciate if you could comment on this. Do you see any 
> problem in my test code?
>
Anybody?
Have I made myself clear enough? If not, I can provide more information 
or explain the problem in more detail.
I just would like to get some feedback!

Cheers

Sascha