From: Roger Pack <rogerpack2005@...>
Date: 2008-11-07T03:29:22+09:00
Subject: Re: Garbage collector segmentation fault

> Hello Roger and thanks for quick reply,
> 
> It is always hard to reproduce a bug in garbage collector as it is 
> unpredictable at best. But calling the same function between 5-10 times 
> always produces the segmentation fault.
> 
> It can only be reproduced in my web environment running rails with 
> webbrick (or any other webserver). I've tried to reproduce the bug in 
> the console but haven't succeeded, maybe because its hard to simulate 
> what the webserver does in the console. If you have any ideas on how to 
> do this please let me know :)

that's tough :)

> I tried with different version of ruby and now I'm using
> ruby 1.8.7 (2008-10-31 revision 0) [x86_64-linux]

You may want to try a newer revision--I assume they all err? [SVN HEAD 
of the 187 branch would be ideal].

I assume that p is a null pointer in this example?

> Below is a GDB backtrace
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 47286927956704 (LWP 23124)]
> garbage_collect () at gc.c:1184
> 1184        if (!(p->as.basic.flags & FL_MARK)) {
> (gdb) bt
> #0  garbage_collect () at gc.c:1184
> #1  0x000000000042e41b in rb_gc () at gc.c:1533
> #2  0x000000000042e439 in rb_gc_start () at gc.c:1550
> #3  0x000000000041b87a in rb_call0 (klass=47286918689040, 
> recv=47286918689080, id=5313, oid=5313,

you might be able to email me a core dump [rogerpack2005@gmail.com] 
but...that's still not quite as nice as having a reproducible 
environment, is it?
I'd say try with SVN HEAD and report back.
Thanks!
-=R
-- 
Posted via http://www.ruby-forum.com/.