Hi,

At Mon, 21 Sep 2009 13:34:31 +0900,
Suraj Kurapati wrote in [ruby-core:25689]:
> The trick is to always work with the Fiber inside the environment 
> (a running thread?) provided by rb_protect().  If you try to do 
> anything to the Fiber (other than #inspect) outside of rb_protect(),
> a segfault occurs (see the NOTE comment in the example below).

Regardless of fiber, uncaught exception causes a segfault.  And
I don't think it's guaranteed to resume a fiber in different
rb_protect scope.

-- 
Nobu Nakada