Workarounds for ruby 1.8.6 segmentations faults

Ruby
1

Hi,

I am running Rails 2.1.0 and ruby-1.8.6 (2008-06-20 patchlevel 230
[i686-linux]. I am experiencing the same segmentation faults that
several others are who are running this version or ruby. Can anyone
recommend a good workaround for these bugs until the Rails Core Team
puts out something official?

Thanks!

Cheri

2

Um, I somehow doubt it’s Rails segfaulting. I’m running the same Ruby
and Rails and have had no issues.

What exactly is throwing the seg faults?

Jason

3

It’s not Rails, it’s Ruby. See Ruby 1.9.0/1.8.7/1.8.6/1.8.5 new releases (Security Fix) - Ruby - Ruby-Forum

4

See also
http://rubyforge.org/tracker/?func=detail&aid=20902&group_id=426&atid=1698

  • Cheri
5

From: Charles Oliver N. [mailto:[email protected]]

try JRuby in the meantime. We’re not affected by those security

issues and run Rails 2.1 fine…

indeed. that’s a great plus for jruby.
will jruby support ruby1.9 and future ruby versions?

thanks and kind regards -botp

6

Charles Oliver N. wrote:

I’ll probably get smacked for this, but you could certainly try JRuby in
the meantime. We’re not affected by those security issues and run Rails
2.1 fine…

Possible roadblock: You’re using native-code libraries that do not have
JRuby analogues.

–
James B.

www.happycamperstudios.com - Wicked Cool Coding
www.jamesbritt.com - Playing with Better Toys
www.ruby-doc.org - Ruby Help & Documentation
www.rubystuff.com - The Ruby Store for Ruby Stuff

7

Peña wrote:

From: Charles Oliver N. [mailto:[email protected]]

try JRuby in the meantime. We’re not affected by those security

issues and run Rails 2.1 fine…

indeed. that’s a great plus for jruby.
will jruby support ruby1.9 and future ruby versions?

Yes, we plan to start adding 1.9 features over the summer and into fall,
with final support being ready around 1.9.1 release time at Christmas.

  • Charlie
8

liquid_rails wrote:

Hi,

I am running Rails 2.1.0 and ruby-1.8.6 (2008-06-20 patchlevel 230
[i686-linux]. I am experiencing the same segmentation faults that
several others are who are running this version or ruby. Can anyone
recommend a good workaround for these bugs until the Rails Core Team
puts out something official?

I’ll probably get smacked for this, but you could certainly try JRuby in
the meantime. We’re not affected by those security issues and run Rails
2.1 fine…

Perhaps an opportunity to try something new?

  • Charlie
9

Wow, we’re also seeing seg-faults with this.

So a possibly vulnerable -p114 or a non-working -p230, nice.

Hmm, I didn’t see problems locally because the ebuild for p230
includes a rollback patch that reverts change 15856. We’ll see what
the official fix is, hopefully it’s soon.

Jason

10

From: [email protected]

Yes, we plan to start adding 1.9 features over the summer and

into fall, with final support being ready around 1.9.1 release

time at Christmas.

wow, very cool indeed.
i’d like to test it on ramaze since ramaze is 1.9 ready.

thanks for jruby
kind regards -botp

11

Peña wrote:

From: [email protected]

Yes, we plan to start adding 1.9 features over the summer and

into fall, with final support being ready around 1.9.1 release

time at Christmas.

wow, very cool indeed.
i’d like to test it on ramaze since ramaze is 1.9 ready.

For what it’s worth, JRuby will support both 1.8 and 1.9 in the same
distribution:

âž” jruby -help
Usage: jruby [switches] [–] [programfile] [arguments]
-0[octal] specify record separator (, if no argument)
-a autosplit mode with -n or -p (splits $_ into $F)
…
–1.8 specify Ruby 1.8.x compatibility (default)
–1.9 specify Ruby 1.9.x compatibility
–version print the version

  • Charlie
12

On 02/07/2008, Jason R. [email protected] wrote:

Wow, we’re also seeing seg-faults with this.

So a possibly vulnerable -p114 or a non-working -p230, nice.

If it segfaults and you did not investigate why you should assume it
is also vulnerable, although probably to a different thing.

Thanks

Michal