From: patrick-may@... (Patrick May)
Date: 2002-08-18T10:22:54+09:00
Subject: Re: Help with a segv in mod_ruby - interpreter bug?

Dave Thomas <Dave@PragmaticProgrammer.com> wrote in message news:<m2bs82pd9w.fsf_-_@zip.local.thomases.com>...
> Armin Roehrl <armin@xss.de> writes:
> 
> > Do you happen to have installed a new (version of a ) library that
> > gets used?
> > 
> > Sth. along the lines of: the library was compiled for version 13.1,
> > but now gets used for version 13.2 or vice versa.
> 
> Well, the problem goes away when I comment out the following three
> lines of code:
> 
>    def nil.empty?
>       true
>    end
> 
> Could this be an interpreter problem?

This sounds like an interpreter problem that we hit while working on
the narf cgi.  Our bug caused the interpreter to segfault.  I isolated
code to cause the fault on cygwin, but that particular series didn't
cause segfaults in linux.

The lines of code in question had to do with nils, too.

Our guess was that it was some type of corrupted memory problem -- the
nil lines would cause the corruption, but something else would have to
walk over the problem to cause a segfault.

~ Patrick