Looks like a x86_64 ruby bug off-hand. Can you attach gdb, reproduce, and provide a stack trace? -HD On Monday 25 June 2007 09:12, Zskdan Zskdan wrote: > ruby 1.8.6 (2007-03-13) [x86_64-linux]