On Jun 27, 2007, at 4:36 PM, Bill Kelly wrote:

> From: "James Edward Gray II" <james / grayproductions.net>
>>
>> On Jun 27, 2007, at 3:43 PM, Tim Hunter wrote:
>>> James Edward Gray II wrote:
>>>> On Jun 26, 2007, at 5:40 PM, Tim Hunter wrote:
>>>>
>>>>> The script works normally now. I suppose I should get  
>>>>> energetic  and work on a small reproduction of the problem.
>>>>
>>>> If anyone has a minimal script that shows this error, please  
>>>> share  it.  I've been in contact with Apple and Leopard is  
>>>> suppose to  ship with Ruby 1.8.6-p36 which is where I found the  
>>>> issue.  They  are willing to patch it though, if we can show the  
>>>> problem.   Unfortunately, both scripts I ran into it with are  
>>>> very non-trivial.
>>>>
>>>> James Edward Gray II
>>>>
>>> Oh, great. I re-installed 1.8.6-p36 and the script runs normally  
>>> now.
>>>
>>> Sigh. Sometimes I hate software.
>> I'm pretty sure the issue is related to threading.  It would  
>> always  show up for me after I had been fetching Web pages or  
>> sending some  email using the networking libraries.
>
> Something like this was brought up on ruby-core last week:
> http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/11505
>
> ``1.8.6 thread support was broken in bad ways. It stayed for three  
> months
>
>  1.8.6-p36 is broken w.r.t. compilation of extensions and has a  
> thread bug.  The bug is much minor than in 1.8.6, but it is  
> nonetheless a bug in a  very "core" part of the standard library.''

Yes, both myself and an Apple employee were trying to follow that  
message train to find example error code and see where the issue was  
resolved in Subversion.  We may have located the relevant patch by  
Nobu in the bug tracker, but that's about it.

James Edward Gray II