From: KOSAKI Motohiro <kosaki.motohiro@...>
Date: 2012-04-24T04:21:17+09:00
Subject: [ruby-core:44568] Re: [ruby-trunk - Bug #6341] SIGSEGV: Thread.new { fork { GC.start } }.join

> kosaki (Motohiro KOSAKI) wrote:
>> I think this is a kind of documentation issue. If you use C, you can't use both thread and fork. It's obvious.
>> And almost people think ruby naturally has the same limitation because ruby is written by C. But rudolf implicitly
>> pointed out some people don't think so.
>>
>> So, if anyone send me a documentation patch, i'll merge it.
>
> Yes, I agree it will help if the documentation will mention that. But the sole existence of a test which uses both thread and fork is somewhat contradictory :)

Just add "skip if NetBSD" idiom into the test. :)
Our test suite aren't intended to test posix issue, it only works for
detecting unintended commit from careless commiter.