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

Mantis Bug Tracker noreply at opencsw.org
Thu Jun 24 14:06:08 CEST 2010


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-06-16 17:18 CEST
====================================================================== 
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?

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

---------------------------------------------------------------------- 
 (0008034) nutznboltz (reporter) - 2010-06-16 17:18
 https://www.opencsw.org/mantis/view.php?id=4399#c8034 
---------------------------------------------------------------------- 
http://redmine.ruby-lang.org/issues/show/2247
says: {{ Also, when compiling with a recent gcc at optimization level -O2
(or higher), util.c throws a number of warnings about breaking
strict-aliasing rules. There is no /easy/ fix for this, but the work-around
is to simply compile that one file with -fno-strict-aliasing ... }}



More information about the bug-notifications mailing list