Hello,

2012/4/24, jshow (Jodi Showers) <jodi / homestars.com>:
> I have tried your example, but unfortunately couldn't cause a crash. I
> experimented with various values of as high as 3000.

It is difficult to reproduce a problem about GC with a small code.
Indeed, my example does not cause SEGV on my another system.

Can you try the following patch?
This is an ad-hoc patch that stops finalizer call at exit.
SEGV should disappear if my guess is right.
If it still causes SEGV, my example is another issue.


diff --git a/eval.c b/eval.c
index 4dddcaa..b2358f8 100644
--- a/eval.c
+++ b/eval.c
@@ -98,7 +98,6 @@ ruby_finalize_1(void)
 {
     ruby_sig_finalize();
     GET_THREAD()->errinfo = Qnil;
-    rb_gc_call_finalizer_at_exit();
 }

 void

-- 
Yusuke Endoh <mame / tsg.ne.jp>