Rails Script Segmentation Fault with Rvm

Rails Script Segmentation Fault with RVM

There's a problem with you RVM installation. which should return

/Users/maletor/.rvm/rubies/ruby-1.9.2-p0/bin/ruby

Upgrade to the latest RVM installation. There was a bug in the 1.0 release with "shell path caching".

$ rvm get head
$ rvm reload
$ rvm repair all
$ rvm use 1.9.2

Segmentation fault in rails / activesupport 3.1 and ruby 1.9.2

It turns out that the combination of devise (1.3.4) and meta_search (1.1.0.pre) results in these segmentation faults. Disabling one of them "solves" the problem. The root cause is either in one of these gems or in ruby itself. See this ruby issue.

segment fault 11 when install ruby 3

after longtime googling and have a lot of issues that I explained before, I found this link
that explained these three command witch help to fix these issues.

$ sudo rm -rf /Library/Developer/CommandLineTools
$ xcode-select --install
$ sudo xcode-select -s /Library/Developer/CommandLineTools

Segmentation fault with Ruby 1.8.7

You could try rebuilding some or all of your gems. It may be related to your shared libraries and .bundle files.

JSON has a compiled extension that might've been corrupted or rendered incompatible.

Webrick crashing with Segmentation Fault on first page load

I had some touble with Webrick too that caused a segementation fault. I only had this on one specific ubuntu box but I didn't have the same error on other ubuntu boxes with the exact same setup. Lately I solved it using thin. To do this add this to your Gemfile:

gem 'thin'

Then run

bundle install
rails server

Segmentation fault' when executing Enumerator#next in rails console

I don't see an issue for this reported against Ubuntu, but I do see one for OS X Lion. You might consider figuring out where exactly to report the issue against 1.9.2 and try to see if anyone in the community there can give you more guidance on how to get a bug report (a) verified as an actual bug and not caused by something else, and (b) where and how to file the bug if it does get verified.

I don't believe you're supposed to create issues directly in the backport page, but at least for reference here are the list of issues on the 1.9.2 backport list.

• https://bugs.ruby-lang.org/projects/ruby-192/issues?set_filter=1

---

Related Topics