From: Harry Ohlsen Date: 2001-12-04T09:01:56+09:00 Subject: [ruby-talk:27387] Strange error behaviour I haven't quite tracked down the precise circumstances yet, but I guess that's why I'm asking :-) ... I have some multi-threaded code. For some reason, when it does something stupid that would normally cause an exception and produce a nice stack trace of where things went wrong, it doesn't seem to output anything. Is this something to do with threading and, in any case, can I organise to see the messages. It's really slow debugging by putting in lots of puts() to see how far the code is getting !!