From: "Mauricio Fernández" <batsman.geo@...>
Date: 2003-03-28T04:42:31+09:00
Subject: Re: Debugging Ruby itself.

On Fri, Mar 28, 2003 at 04:14:09AM +0900, Eric Hodel wrote:
> Mauricio Fern?ndez (batsman.geo@yahoo.com) wrote:
> 
> > On Thu, Mar 27, 2003 at 02:29:58PM +0900, John Carter wrote:
> > 
> > > Any Ruby specific suggestions for hunting this type of bug?
> > > 
> > > I'm on RedHat Linux 8.0 on a Pentium 4 using gcc 3.2.2
> > 
> > It could be GCC's fault. I was doing something heavily threaded too
> > (from 20 to 150+ threads) which opened lots of connections to a dictd
> > server and found that the problem would only happen when compiling with
> > gcc 3.2, and moreover only when targeting i386, but not sure on this
> > one, have forgotten :-)
> 
> To reduce the likelihood of it being GCC's fault, compile ruby and any
> extensions with no flags higher than -O
> 
> To see what your ruby was compiled with:
> 
> $ ruby -r rbconfig -e "puts Config::CONFIG['CFLAGS']"
> 
> FWIW, FreeBSD has problems with -march=pentium4 ...
> 

This is what I found in my case...

The BUG first happened w/ Debian's 1.6.8-3 binary, shortly after they
began building with GCC 3.2 (w/ -O2 AFAIK). It didn't show up when
compiled with gcc 2.95.4. Moreover, the last CVS snapshot I got ran OK
until I compiled it w/ gcc 3.2 and then I got the BUG again.

-- 
 _           _                             
| |__   __ _| |_ ___ _ __ ___   __ _ _ __  
| '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ 
| |_) | (_| | |_\__ \ | | | | | (_| | | | |
|_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_|
	Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com

"Who is General Failure and why is he reading my hard disk?"
Microsoft spel chekar vor sail, worgs grate !!
	-- Felix von Leitner, leitner@inf.fu-berlin.de