[#35027] [Ruby 1.9-Bug#4352][Open] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s) — "James M. Lawrence" <redmine@...>

Bug #4352: [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s)

16 messages 2011/02/01

[#35114] [Ruby 1.9-Bug#4373][Open] http.rb:677: [BUG] Segmentation fault — Christian Fazzini <redmine@...>

Bug #4373: http.rb:677: [BUG] Segmentation fault

59 messages 2011/02/06

[#35171] [Ruby 1.9-Bug#4386][Open] encoding: directive does not affect regex expressions — mathew murphy <redmine@...>

Bug #4386: encoding: directive does not affect regex expressions

9 messages 2011/02/09

[#35237] [Ruby 1.9-Bug#4400][Open] nested at_exit hooks run in strange order — Suraj Kurapati <redmine@...>

Bug #4400: nested at_exit hooks run in strange order

12 messages 2011/02/15

[ruby-core:35303] Re: [Ruby 1.9-Bug#4373] http.rb:677: [BUG] Segmentation fault

From: Benoit Daloze <eregontp@...>
Date: 2011-02-18 21:36:21 UTC
List: ruby-core #35303
On 6 February 2011 18:43, Christian Fazzini <redmine@ruby-lang.org> wrote:
> Issue #4373 has been updated by Christian Fazzini.
>
>
> Openssl is already installed via macports. Actually, the replication is quite simple. I have come up with a narrowed step-by-step procedure:
>
> 1) Install rails
> 2) Create a new rails project
> 3) Open gem file and include the following gems: gem 'twitter', :git => 'http://github.com/jnunemaker/twitter.git'
> 4) Bundle install
> 5) Start rails server (rails s)
> 6) Start rails console (rails c)
> 7) In rails console, type: Twitter.user("sferik").location (or any Twitter gem related commands at: http://twitter.rubyforge.org/)
>
> That's when the error comes up. As I am aware, the Twitter gem uses the Faraday gem which somewhat uses /net/http.rb
> ----------------------------------------
> http://redmine.ruby-lang.org/issues/show/4373
>
> ----------------------------------------
> http://redmine.ruby-lang.org
>
>

I can not reproduce using these steps with trunk (ruby 1.9.3dev
(2011-02-18 trunk 30894) [x86_64-darwin10.6.0]).

> Shota, what approach can I take to overcome this issue? What do you suggest?
> Perhaps, I can remove RVM completely? Or uninstall OpenSSL via MacPorts?
> I could also do a reformat of the entire system, but that would take far too long and much effort to backup and restore.

I'd probably try first to uninstall OpenSSL from MacPorts (or maybe
move /opt to be sure Ruby won't look there).
Then reinstalling rvm (I once had some really weird issue, and
reinstalling rvm solved it).
You can of course just `mv ~/.rvm ~/.rvm_old` to not lose your old installation.
And it would be interesting to see if it also happens with trunk (rvm
install ruby-head).

In This Thread