Hi,

At Thu, 23 May 2002 01:03:19 +0900,
Paul Brannan wrote:
> > That [BUG] in the error I got was odd - where did that come from?
> >
> > Is there anything I can do to see what might be causing the segfault? It's
> > hard to keep running that script over and over since it bring the database
> > server to it's knees (not hard to do with this server...)
> 
> It can mean that:
> 
> 1) There is a bug in an extension you are using.  This seems likely to
>    me.  If you want to find out exactly where the bug is, then you can
>    run gdb (or your favorite debugger) on the ruby interpreter.

I'm not sure about that library.

> 2) There is a bug in the Ruby interpreter.  If this is the case, you
>    need to write a small test program (should be the smallest possible
>    program that demonstrates the problem) and post a bug report
>    (instructions at http://www.ruby-lang.org/cgi-bin/ruby-bugs).

If so, it may be fixed in more recent version.  Try with latest
snapshot.

> 3) You have your stack size set too low, and Ruby is running out of
>    stack space.

No, Ruby raises SystemStackError in such case, or can do
nothing, even displaying the [BUG] message.

> I think there might be a few more less likely possibilities, but I can't
> think of what they are at the moment.

Also I can't say nothing without seeing the actual code.

-- 
Nobu Nakada