On 3/24/10 9:13 PM, Joerg Sonnenberger wrote: > The point is that you don't really get that. Consider mutexes currently > hold by a different thread in the original program. May I strongly > advise you to first identify exactly where Ruby is failing and based on > that let us decide how it can be fixed.
I'll take a look into what is going on there. Ruby 1.9 is rather... complicated internally, and NetBSD is not (currently) a supported OS. I know their thread code works as-is on linux, solaris, and macos, so whatever they are doing is "safe" from their point of view. --Michael