问题描述
是只有我,还是 Ruby 1.9.3 在运行 RSpec 时引入了频繁的分段错误?
Is it just me, or has Ruby 1.9.3 introduced frequent segmentation faults when running RSpec?
自从升级到 1.9.3 后,我发现启动时间明显加快,但是在大约 50% 的时间运行 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.
我从 Ruby 获得的输出位于 http://pastebin.com/89YmpzaJ我的 Gemfile 位于 http://pastebin.com/L6r73Max
The output that I am getting from Ruby is at http://pastebin.com/89YmpzaJand my Gemfile is at http://pastebin.com/L6r73Max
有谁知道是什么原因造成的?我在 CI 服务器和本地开发机器上都看到了这个问题.
Does anyone know what could be causing this? I am seeing this problem on both my CI server and my local development machine.
推荐答案
pry-doc/yard 似乎存在问题,可能导致 yard 中出现段错误.我所知道的最好的解决方法是不使用 pry-doc.为方便起见,Pry-rails 依赖于 pry-doc,因此除了从 Gemfile 中删除 pry-doc 之外,您还需要修改 pry-rails 以删除其对 pry-doc 的依赖.
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.
(我已经分叉了 pry-rails 来做到这一点:https://github.com/chrisfarber/撬轨.)
(I've already forked pry-rails to do that: https://github.com/chrisfarber/pry-rails.)
这篇关于Ruby 1.9.3-p0 和 RSpec 导致频繁的分段错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!