you could attach gdb to it to get a backtrace.
I know there used to be a bug in 1.9.1 that would cause this behavior, 
but thought it was fixed...
seems to work fine here on 32 bit
ruby 1.9.2p0 (2010-08-18) [i386-mingw32]

-- 
Posted via http://www.ruby-forum.com/.