From: John Carter <john.carter@...>
Date: 2003-03-27T14:29:58+09:00
Subject: Debugging Ruby itself.

For various reasons I'm using the CVS latest version of Ruby....

Now I have 3500 lines of _very_ _very_ threaded (about 100 threads) ruby
doing lots and lots of socket I/O to strange exotic hardware.

Ruby itself sometimes crashes (not in the same place).

So I haven't been able to produce a small test set. I can't send Matz all
the weird hardware, so I'm on my own here....

Any Ruby specific suggestions for hunting this type of bug?

I'm on RedHat Linux 8.0 on a Pentium 4 using gcc 3.2.2



John Carter                             Phone : (64)(3) 358 6639
Tait Electronics                        Fax   : (64)(3) 359 4632
PO Box 1645 Christchurch                Email : john.carter@tait.co.nz
New Zealand

John's law :-

All advances in computing have arisen through the creation of an
additional level of indirection, the trick is to work out which
indirection is actually useful.