From: ts <decoux@...>
Date: 2002-08-17T20:57:39+09:00
Subject: Re: Help with a segv in mod_ruby - interpreter bug?

>>>>> "D" == Dave Thomas <Dave@PragmaticProgrammer.com> writes:

D>    def nil.empty?
D>       true
D>    end

 Yes, the problem is on these line


D>    #0  0x402c06f5 in st_lookup (table=0x81645f0, 
D>        key=0xc19 <Address 0xc19 out of bounds>, value=0xbfffd140) at st.c:253
D>    #1  0x4026e895 in search_method (klass=1079869732, id=3097, origin=0xbfffd17c)
D>        at eval.c:250
D>    #2  0x4026e8e1 in rb_get_method_body (klassp=0xbfffd1cc, idp=0xbfffd1bc, 
D>        noexp=0xbfffd1c0) at eval.c:268
D>    #3  0x402784b4 in rb_call (klass=1079869732, recv=4, mid=3097, argc=1, 
D>        argv=0xbfffd1ec, scope=1) at eval.c:4582
D>    #4  0x40278869 in rb_funcall (recv=4, mid=3097, n=1) at eval.c:4679

 recv=4    ===> self = nil
 mid=3097  ===> method is #singleton_method_added

 ruby search the method #singleton_method_added in NilClass

D> Could this be an interpreter problem?

 interpreter or mod_ruby problem

 If you can give your complete configuration (apparently you run 1.6.7,
 right ?) and your script to try to reproduce the segfault ?


Guy Decoux