The traceback appears below.  This is an unpatched snapshot checked out
of svn on 10/23/07.  Running on i686 Gentoo Linux, built with gcc
version 4.1.2
CFLAGS='-g'

I will try to create a self contained test case, but any thoughts
on what is happening might be very helpful.

Has anyone else run into similar crashes during
startup of a Ruby thread?

Thanks in Advance,

- brent
----------------------

---> Starting thread core
---> Starting thread processing
/home/brent/esp2/lib/msg.rb:163: -- control frame ----------
c:0003 p:0005 s:0005 b:0005 l:001a24 d:000004 BLOCK 
/home/brent/esp2/lib/msg.rb:163
c:0002 p:---- s:0003 b:0003 l:000002 d:000002 FINISH
c:0001 p:---- s:0001 b:-001 l:000000 d:000000 ------
---------------------------
-- backtrace of native function call (Use addr2line) --
0x80f916a
0x8117da8
0x8117e47
0x80c28e9
0xb7fc2420
0x80e8352
0x80f64a2
0x80f1554
0x80f6e72
0x80f0058
0x80f01da
0x80f9f99
0x80f9552
0xb7f9d4bb
0xb7ed54de
-------------------------------------------------------
[BUG] Segmentation fault
ruby 1.9.0 (2007-10-23) [i686-linux]

Aborted
brent@ESPlaptop ~/valveMoves $ addr2line -e /usr/local/bin/ruby19
0x80f916a
0x8117da8
0x8117e47
0x80c28e9
0xb7fc2420
0x80e8352
0x80f64a2
0x80f1554
0x80f6e72
0x80f0058
0x80f01da
0x80f9f99
0x80f9552
0xb7f9d4bb
0xb7ed54de
-/home/brent/ESP/gen2/software/ruby/ruby19/vm_dump.c:588
/home/brent/ESP/gen2/software/ruby/ruby19/error.c:212
/home/brent/ESP/gen2/software/ruby/ruby19/error.c:228
/home/brent/ESP/gen2/software/ruby/ruby19/signal.c:543
??:0
/home/brent/ESP/gen2/software/ruby/ruby19/variable.c:1454
/home/brent/ESP/gen2/software/ruby/ruby19/insnhelper.ci:1023
/home/brent/ESP/gen2/software/ruby/ruby19/insns.def:225
/home/brent/ESP/gen2/software/ruby/ruby19/vm.c:1163
/home/brent/ESP/gen2/software/ruby/ruby19/vm.c:583
/home/brent/ESP/gen2/software/ruby/ruby19/vm.c:622
/home/brent/ESP/gen2/software/ruby/ruby19/thread.c:316
/home/brent/ESP/gen2/software/ruby/ruby19/thread_pthread.ci:177
??:0
??:0