On Tue, Apr 24, 2012 at 12:13 PM, NARUSE, Yui <naruse / airemix.jp> wrote:
> (2012/04/24 19:44), KOSAKI Motohiro wrote:
>>> kosaki (Motohiro KOSAKI) wrote:
>>>> On Mon, Apr 23, 2012 at 11:17 PM, Yusuke Endoh <mame / tsg.ne.jp> wrote:
>>>> =A0> I suggest to make Kernel#fork raise a NotImplementedError on NetB=
SD
>>>> =A0> 5.0+.
>>>> =A0> Fortunately, the tests already have a guard for NotImplementedErr=
or
>>>> =A0> because there is a supported platform that does not support
>>>> =A0> Kernel#fork (you know, windows).
>>>> =A0> Even on the platform, SEGV is not allowed, in principle.
>>>>
>>>> =A0No. it works if user don't use threads. So, one option is, fork aft=
er
>>>> =A0thread.new raise an exception on all platform.
>>>
>>> It is wrong.
>>> Ruby 1.9 makes timer thread even if there is only the main thread.
>>
>> You don't understand the issue. On other OSs, async-signal-unsafe functi=
on usage
>> makes unlocked libc lock issue. therefore our current fork code works.
>> It kill timer thread
>> at once.
>
> You don't know the original issue, what you are saying seems recent one.
> see also http://bugs.ruby-lang.org/issues/show/270

I don't? Why? Even though I joined bug#270 discussion.