Issue #2127 has been updated by Suraj Kurapati. Hi, Nobu Nakada wrote: > Regardless of fiber, uncaught exception causes a segfault. Thanks, this is good to know. > I don't think it's guaranteed to resume a fiber in different > rb_protect scope. Why is that? Does each rb_protect scope have a different running thread (with a different stack + heap)? Is there danger of a cross-thread violation? Should I try to store the original rb_protect scope into a variable and reuse it when resuming my Fiber? What do you suggest? Thanks for your consideration. (Sorry for asking so many questions!) ---------------------------------------- http://redmine.ruby-lang.org/issues/show/2127 ---------------------------------------- http://redmine.ruby-lang.org