Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it just me, or has Ruby 1.9.3 introduced frequent segmentation faults when running RSpec?
Since upgrading to 1.9.3, I find startup time is noticeably quicker, however I get segmentation faults when running RSpec around 50% of the time.
The output that I am getting from Ruby is at http://pastebin.com/89YmpzaJ
and my Gemfile is at http://pastebin.com/L6r73Max
Does anyone know what could be causing this? I am seeing this problem on both my CI server and my local development machine.
There appears to be a problem with pry-doc/yard that can cause segfaults in yard. The best workaround I know of is to simply not use pry-doc. Pry-rails depends on pry-doc as a convenience, so in addition to removing pry-doc from your Gemfile, you will need modify pry-rails to remove its dependency on pry-doc.
(I’ve already forked pry-rails to do that: https://github.com/chrisfarber/pry-rails.)