From: jordon@...
Date: 2017-10-10T22:30:30+00:00
Subject: [ruby-core:83201] [Ruby trunk Bug#9505] Bug that should cause SystemStackError segfaults under Ruby 2.1

Issue #9505 has been updated by 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 in 2.4. I just got this today on the latest stable.

----------------------------------------
Bug #9505: Bug that should cause SystemStackError segfaults under Ruby 2.1
https://bugs.ruby-lang.org/issues/9505#change-67144

* Author: Perceptes (Jimmy Cuadra)
* Status: Feedback
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-darwin13.0]
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
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



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>