From: Sean Chittenden <sean@...>
Date: 2002-09-29T18:15:16+09:00
Subject: Re: ruby bug in tight loops?  (was: Re: Matz, if you're reading, please scan this email)

> S> Good catch, I fixed this in the CVS version, however this is a
> S> different problem than the one I am having.  Use test case xml_parser4
> S> as it doesn't touch any of the IO routines (though if you update and
> S> try again, you should get the same bug).  Check out the other post
> 
> pigeon% tests.rb -n xml_parser4
> Running tests xml_parser4
> Loaded suite libxml
> Started...
> ..
> Finished in 0.007966 seconds.
> 1 runs, 13 assertions, 0 failures, 0 errors
> pigeon%

Yup, that's right.  Now add -i 0 to the argument list and watch it
core after a few min.  This is a bug that comes out when you stress
test a module.  -sc

-- 
Sean Chittenden