I still get this happening a lot with my Rubyx linux ruby script.

I can get it to happen every time with a recent ruby snapshot, without debug 
info. Unfortunately it doesn't occur if I build ruby with '-g'

Example:

andrew@zen rubyx $ ruby ./rubyx
[BUG] unknown node type 0
ruby 1.8.2 (2004-11-27) [i686-linux]

Aborted

andrew@zen rubyx $ gdb /bin/ruby
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db 
library "/pkg/glibc.1/lib/libthread_db.so.1".

(gdb) run ./rubyx
Starting program: /bin/ruby ./rubyx
[Thread debugging using libthread_db enabled]
[New Thread -1209730416 (LWP 3334)]
[BUG] unknown node type 0
ruby 1.8.2 (2004-11-27) [i686-linux]

Program received signal SIGABRT, Aborted.
[Switching to Thread -1209730416 (LWP 3334)]
0xffffe410 in ?? ()

Ruby was configured with --enable-pthread on a NPTL enabled glibc.

If anyone (within reason ;)) thinks they can get any further with gdb on this 
machine, I'm happy to let them have ssh access.

I'm still smarting from my humiliating attempts to locate the problem with 
valgrind ;)

Andrew Walrond