From: Roger Pack <rogerdpack@...>
Date: 2009-03-11T20:07:30+09:00
Subject: [ruby-core:22841] Re: [Bug #744] memory leak in callcc?

> #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 valgrind would help?
-=r