workarounds for ruby 1.8.6 segmentations faults

[liquid_rails]

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

 

[Jason Roelofs]

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

 

[liquid_rails]

It's not Rails, it's Ruby. See http://www.ruby-forum.com/topic/157034

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

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

 

[liquid_rails]

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

- Cheri

It's not Rails, it's Ruby. Seehttp://www.ruby-forum.com/topic/157034

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

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

 

[Charles Oliver Nutter]

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

 

[Peña, Botp]

RnJvbTogQ2hhcmxlcyBPbGl2ZXIgTnV0dGVyIFttYWlsdG86Y2hhcmxlcy5udXR0ZXJAc3VuLmNv
bV0gDQojIHRyeSBKUnVieSBpbiB0aGUgbWVhbnRpbWUuIFdlJ3JlIG5vdCBhZmZlY3RlZCBieSB0
aG9zZSBzZWN1cml0eSANCiMgaXNzdWVzIGFuZCBydW4gUmFpbHMgMi4xIGZpbmUuLi4NCg0KaW5k
ZWVkLiB0aGF0J3MgYSBncmVhdCBwbHVzIGZvciBqcnVieS4NCndpbGwganJ1Ynkgc3VwcG9ydCBy
dWJ5MS45IGFuZCBmdXR1cmUgcnVieSB2ZXJzaW9ucz8NCg0KdGhhbmtzIGFuZCBraW5kIHJlZ2Fy
ZHMgLWJvdHANCg==

 

[James Britt]

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 Britt

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

 

[Charles Oliver Nutter]

From: Charles Oliver Nutter [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

 

[Peña, Botp]

RnJvbTogQ2hhcmxlcy5PLk51dHRlckBzdW4uY29tIA0KIyBZZXMsIHdlIHBsYW4gdG8gc3RhcnQg
YWRkaW5nIDEuOSBmZWF0dXJlcyBvdmVyIHRoZSBzdW1tZXIgYW5kIA0KIyBpbnRvIGZhbGwsIHdp
dGggZmluYWwgc3VwcG9ydCBiZWluZyByZWFkeSBhcm91bmQgMS45LjEgcmVsZWFzZSANCiMgdGlt
ZSBhdCBDaHJpc3RtYXMuDQoNCndvdywgdmVyeSBjb29sIGluZGVlZC4NCmknZCBsaWtlIHRvIHRl
c3QgaXQgb24gcmFtYXplIHNpbmNlIHJhbWF6ZSBpcyAxLjkgcmVhZHkuDQoNCnRoYW5rcyBmb3Ig
anJ1YnkNCmtpbmQgcmVnYXJkcyAtYm90cA0KDQo=

 

[Jason Roelofs]

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

 

[Charles Oliver Nutter]

From: (e-mail address removed)
# 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

 

[Michal Suchanek]

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