From: Henrik Zagerholm <henke@...>
Date: 2008-12-22T17:40:18+09:00
Subject: Re: Garbage collector segmentation fault

Roger Pack wrote:
> 
>> I get this every now and then when running some ruby / c++ methods from
>> within rails.
>> It looks like ruby's garbage collector once again makes bad decisions...
>> 
>> Program received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread 47432141183712 (LWP 30617)]
>> garbage_collect () at gc.c:1184
>> 1184        if (!(p->as.basic.flags & FL_MARK)) {
>> 
>> 
>> I've posted the bug to the ruby bug hunting system but haven't heard
>> nothing yet. I think this is the biggest problem with ruby. The core
>> development is slow and badly maintained.
> 
> Check http://www.ruby-forum.com/topic/170608#new it has some recent GC 
> patches that might help.  Also could submit a report to 
> redmine.ruby-lang.org [esp. if reproducible].
> Thanks!
> -=R

Hi Roger and thanks for the info.

I'll see if I can try this out. The wrapper code is made with Swig so it 
could be a swig problem. This is whay makes it soo hard to debug.

Cheers,
Henke
-- 
Posted via http://www.ruby-forum.com/.