From: Laurent Sansonetti <laurent.sansonetti@...>
Date: 2007-07-01T04:27:52+09:00
Subject: Re: Apple reportedly to ship with ruby 1.8.6-p36 unless informed what to patch

Hi,

For the moment I have been unable to reproduce the problem on my
environment (Leopard, ruby-1.8.6-p36 with --enable-pthread). James
graciously sent me some (private) code that triggers the bug on his
environment, but it doesn't happen on mine.

On Tiger with p36, we can reproduce the problem very easily with
--enable-pthread, but without --enable-pthread the bug seems to have
disappeared.

# We didn't receive (yet) any feedback regarding this bug from our
Leopard users community, which counts a non-negligible number of
people using Ruby.

I would be willing to apply any patch that would fix the problem if I
can manage to reproduce the bug on Leopard, but I have the feeling
that the problem might be elsewhere. I will continue to investigate in
the meantime.

Thanks a lot,
Laurent, Apple Inc.

On 6/30/07, James Edward Gray II <james@grayproductions.net> wrote:
> On Jun 30, 2007, at 4:51 AM, Urabe Shyouhei wrote:
>
> > Hi,
> >
> > James Edward Gray II wrote:
> >> What Apple was asking me for today is a small code snippet that shows
> >> the problem.  If anyone has such a thing, please share.
> >
> > I've not yet succeed to make one, but perhaps Nobu did.  He gave us
> > two
> > patches:
> >
> > http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-dev/30822
> > http://rubyforge.org/tracker/?
> > func=detail&aid=11507&group_id=426&atid=1698
> >
> > Would you mind trying them?
>
> Yeah, we have found the fixes.  What we need is to reliably be able
> to see the problem.  That way Apple can decide if they need to resort
> to a fix.
>
> James Edward Gray II
>
>