[bug-notifications] [ruby 0004399]: Segmentation Fault in Garbage Collection for Ruby 1.8.7 prior to Dec 2009

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4399 
====================================================================== 
Reported By:                nutznboltz
Assigned To:                bwalton
====================================================================== 
Project:                    ruby
Issue ID:                   4399
Category:                   regular use
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
====================================================================== 
Date Submitted:             2010-04-16 18:09 CEST
Last Modified:              2010-10-31 13:39 CET
====================================================================== 
Summary:                    Segmentation Fault in Garbage Collection for Ruby
1.8.7 prior to Dec 2009
Description: 
A known bug exists in Ruby that causes it crash with segmentation faults
(SIGSEGV, signal 11, etc.) when it allocates objects frequently.

This is causing the Ops Code Chef client to crash on our Solaris 10
systems.

A upstream fix was released.  Could someone rebuild the OpenCSW Ruby from
the latest 1.8.7 sources?

====================================================================== 

---------------------------------------------------------------------- 
 (0008426) bwalton (manager) - 2010-10-31 13:39
 https://www.opencsw.org/mantis/view.php?id=4399#c8426 
---------------------------------------------------------------------- 
Ok, there are updated ruby packages available here:
http://buildfarm.opencsw.org/experimental.html#ruby

Aside from the patch to (hopefully) fix the GC segfault, there is also a
change to the libruby.so.1 SONAME.  These changes will likely break binary
gems and I'm still determining the best course of action (short term,
simply install CSWrubydev).  You should still be able to perform the
testing required to ensure the GC issue is or is not handled though.