From: Dossy <dossy@...>
Date: 2002-06-03T22:54:34+09:00
Subject: Re: Ruby 1.7.2 dieing of segfault  (was Re: Ruby 1.6.7 dieing of segfault)

On 2002.06.02, Nobuyoshi Nakada <nobu.nokada@softhome.net> wrote:
> 
> If you use extension libraries, possibly it may be due to those
> libraries.

Indeed, my hunch is that dbd_oracle is NOT thread-safe.

> > I'll try to set up some breakpoints and catch the problem before
> > it manifests, but I don't know how successful I'll be.  Any
> > hints at debugging Ruby will be much appreciated.  :-)
> 
> Anyway, I can say nothing more now.  Can't you make a snippet
> reproduce it?

I don't know what's causing it, so I can't create a small snippet
of code to reproduce it.

Once I have a reproducible test case, I'll provide it.

In the meanwhile, can anyone give me any pointers as to how to
do root cause analysis for this kind of problem?  Are there good
functions in the core to breakpoint?  Otherwise, I'll just have
to keep stepping through the GC code and inspect before and after
of all the variables (ouch!) to see what code is corrupting what.
That'll suck ...

-- Dossy

-- 
Dossy Shiobara                       mail: dossy@panoptic.com 
Panoptic Computer Network             web: http://www.panoptic.com/ 
  "He realized the fastest way to change is to laugh at your own
    folly -- then you can let go and quickly move on." (p. 70)