From: v.ondruch@...
Date: 2014-12-03T13:58:35+00:00
Subject: [ruby-core:66659] [ruby-trunk - Bug #10460] Segfault instead of	stack level too deep

Issue #10460 has been updated by Vit Ondruch.


I've got similar snippet:

~~~
describe "SEGV" do
  let(:foo) do
    foo
  end

  it "crashes" do
    foo
  end
end
~~~

It always fails with ruby 2.1.5p273 (2014-11-13 revision 48405) [x86_64-linux]

It sometimes passes and other time fails with ruby 2.2.0preview2 (2014-11-28 trunk 48628) [x86_64-linux]

----------------------------------------
Bug #10460: Segfault instead of stack level too deep
https://bugs.ruby-lang.org/issues/10460#change-50270

* Author: Arne Brasseur
* Status: Open
* Priority: High
* Assignee: Nobuyoshi Nakada
* Category: core
* Target version: current: 2.2.0
* ruby -v: ruby 2.2.0dev (2014-10-29 trunk 48188) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
The code to trigger this can be found here: https://gist.github.com/mbj/31163a8e712573877268

Also have a look at the comments there. A lot of different people tried it, in some cases it segfaults, in others it doesn't. It seems to have to do with version of gcc or specific CFLAGS. 

I can reproduce the problem for 2.1.3, 2.1.4, and trunk.

---Files--------------------------------
rspec_ruby_segfault.rb (233 Bytes)
sample_output (26 KB)


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