On Sun, Mar 28, 2004 at 09:42:42AM +0900, why the lucky stiff wrote:
> Mauricio Fern?ndez wrote:
> >Happens in both 1.9.0 (2004-03-25) and ruby 1.8.1 (2003-12-25).
> >
> >Program received signal SIGSEGV, Segmentation fault.
> >0x080b0a34 in st_lookup (table=0x401f4d90, key=4369, value=0xbffef078) at 
> >st.c:258
> >258         hash_val = do_hash(key, table);
> 
> batsman, what is happening with this bug?  If you're still getting this, 
> I'd really like to see a script.  If you're not getting it, can you say 
> why you were getting it?  Just don't want to see this sort of scary 
> happenin.

I'm working on it -- the bug happens during some rather long unit tests
and I want to isolate the test case responsible for this. You can expect
more news soon.

BTW, the unit tests are proving to be a great crash test suite for ruby,
I'm getting all sorts of crashes (segfault, unknown node, method xxx
called on finalized object, etc) and infinite loops ;)

-- 
Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com

Beeping is cute, if you are in the office ;)
	-- Alan Cox