Bug #9505: Bug that should cause SystemStackError segfaults under Ruby 2.1

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-darwin13.0]

[Perceptes (Jimmy Cuadra)]

Using rspec-core.3.0.0.beta1 and ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-darwin13.0]:

require "rspec"
require "rspec/autorun"

describe "Ruby 2.1 segfault" do
  let(:argument) { double }

  subject { subject.new(double) }

  it "will segfault" do
    subject
  end
end

Running this program under Ruby 2.0 results in a SystemStackError. Under Ruby 2.1, Ruby segfaults.

Crash log: https://gist.github.com/jimmycuadra/8892336
Segfault output: https://gist.github.com/jimmycuadra/8892213

[hsbt (Hiroshi SHIBATA)]

I can reproduce it on Ruby 2.1.1p28. and ruby-trunk(r44894) got SystemStackError.

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Feedback

Please try your code with Ruby 2.1.1

[danielfone (Daniel Fone)]

I can reproduce almost exactly this issue on 2.1.1p97 p76. Full details and steps I used to reproduce are in https://github.com/danielfone/rspec-memoization-segfault

[jafergus (James Ferguson)]

I've reproduced the same thing with two doubles that reference each other. Also on 2.1.1-p76.

See: https://github.com/JamesFerguson/rspec-mocks-test

[lukeasrodgers (Luke Rodgers)]

For what it's worth, this appears to be fixed in ruby-2.2.0-preview2.

[envygeeks (Jordon Bedwell)]

lukeasrodgers (Luke Rodgers) wrote:

For what it's worth, this appears to be fixed in ruby-2.2.0-preview2.

This still happens on 2.4.
I just got this today on the latest stable.

[wanabe (_ wanabe)]

• Related to Bug #13412: Infinite recursion with define_method may cause silent SEGV or cfp consistency error added

[jeremyevans0 (Jeremy Evans)]

• Status changed from Feedback to Closed
• Backport deleted (1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN)