Bug 453060 - Ruby on Rails: strange errors, segmentation faults and double free or corruption
Ruby on Rails: strange errors, segmentation faults and double free or corruption
Status: CLOSED DUPLICATE of bug 452825
Product: Fedora
Classification: Fedora
Component: ruby (Show other bugs)
9
i386 Linux
low Severity urgent
: ---
: ---
Assigned To: Akira TAGOH
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-26 20:10 EDT by Efren Yevale
Modified: 2008-06-26 21:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-06-26 21:51:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Efren Yevale 2008-06-26 20:10:40 EDT
Description of problem:
Strange behaviour on Rails 2.1.0 when upgrading using yum.

Some times errors arise like ("wrong argument type Fixnum (expected Proc)"),
some times Webrick and Mongrel crashes due to segmentation faults
("form_tag_helper.rb:431: [BUG] Segmentation fault") and some other times ruby
gets frozen with double free or corruption ("*** glibc detected *** ruby: double
free or corruption (out): 0x094200c0 ***").

Version-Release number of selected component (if applicable):
ruby 1.8.6 (2008-06-20 patchlevel 230) [i386-linux]

How reproducible:
Upgrade ruby to ruby-1.8.6.230-2.fc9.i386.

Steps to Reproduce:
1. Install previous Ruby from repositories
2. Install rubygems from www.rubygems.org
3. Install Rails 2.1.0
4. Upgrade Ruby to ruby-1.8.6.230-2.fc9.i386
  
Actual results:
Crashes and unexpected behaviour on Rails.

Expected results:
Rails running normally.

Additional info:
Found related information in the comments on
http://weblog.rubyonrails.org/2008/6/21/multiple-ruby-security-vulnerabilities
Comment 1 Akira TAGOH 2008-06-26 21:51:07 EDT

*** This bug has been marked as a duplicate of 452825 ***

Note You need to log in before you can comment on or make changes to this bug.