Hi,

Sorry for being late.

In message "Re: Rails on Altix ia64"
    on Wed, 18 May 2005 06:25:31 +0900, "Adam P. Jenkins" <ajenkins / interactivesupercomputing.com> writes:

|/home/ajenkins/deploy/lib/ruby/1.8/timeout.rb:41: [BUG] Segmentation fault
|ruby 1.8.3 (2005-05-12) [ia64-linux]
|Aborted
|
|The code at timeout.rb:41 is a call to Thread.start.  I tried modifying
|timeout to not spawn a thread, and then I'd get segfaults elsewhere,
|always at a call to Thread.start.  So it seems to have something to do
|with threading, since single threaded code seems to work fine.  When I
|look at the core dumps, the segfault is always in gc_mark(), at
|gc.c:715.  The ptr parameter to gc_mark always has the value 8.  gc_mark
|tries to treat this as a pointer, and gets a segfault.  I didn't
|understand the code in gc.c enough to get much farther in figuring out
|how this value got there.

The ptr value should not be 8 in any case.  It must be caused by a bug
somewhere.  Can you show us stack trace (by gdb's "where" command)?

							matz.