I am continuing to see random segfaults on x86_64, especially with god
(http://god.rubyforge.org/), which makes liberal use of threads and
forking.

*** glibc detected *** free(): invalid pointer: 0x00000000012b7724 ***
*** glibc detected *** free(): invalid pointer: 0x00000000012b7724 ***

./gems/local/gems/god-0.7.8/bin/../lib/god/event_handler.rb:35: [BUG]
Segmentation fault
/custom/lib/ruby/1.8/net/smtp.rb:462: [BUG] Segmentation fault
/custom/lib/ruby/1.8/timeout.rb:92: [BUG] Segmentation fault
./gems/local/gems/god-0.7.12/bin/../lib/god/process.rb:193: [BUG]
Segmentation fault
/custom/lib/ruby/1.8/net/http.rb:439: [BUG] Segmentation fault

#0  0x00007f7d5efa307b in raise () from /lib/libc.so.6
#1  0x00007f7d5efa484e in abort () from /lib/libc.so.6
#2  0x00007f7d5f596410 in rb_bug (fmt=0x7f7d5f62c195 "Segmentation
fault") at error.c:213
#3  0x00007f7d5f5fd2af in sigsegv (sig=<value optimized out>) at signal.c:634
#4  0x00007f7d5efa3110 in killpg () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()

So far I've been unable to come up with a reproducible test case, but
I've managed to narrow the problem down to mbari2. Vanilla ruby 1.8.7
does not have this issue, whereas 1.8.7+mbari2 will segfault randomly
every few days.

Perhaps it is worth backporting thread anchors from ruby 1.8 HEAD?

  Aman

On Sat, Feb 21, 2009 at 2:01 PM, Roger Pack <rogerdpack / gmail.com> wrote:
>> I pushed an update to the patches onto github last night that seems to
>> improve
>> stability of the MBARI patches on the x86_64 platform.  ¨Âôèåòðìáôæïòí>> seem to be working
>> great, but the x86_64 still has exhibits vexing, very occasional segfaults.
>>
>> I'll be working on it through this rainy weekend.  ¨Âãáóåéôɧ>> confident I can (eventually)
>> fix it.
>
> I wish I had an easy to reproduce script for it but don't [will keep
> my eye out for it, though].
> As a note, mine was having problems on 32-bit
> ruby 1.8.7 (2009-2-13 MBARI 7/0x8770 on patchlevel 72) [i686-linux]
> but that was a slightly older version. I'll update to the latest.
> Thanks!
> -=r
>
>