Issue #10460 has been updated by Andrew M.

File rspec_ruby_segfault.rb added
File sample_output added

Ran into this issue today when I accidentally created a stack overflow in my RSpec tests:

* ruby 2.1.5p273 (2014-11-13 revision 48405, [i686-linux]
* rspec 2.13.1

Attached is code which (sometimes) reproduces the problem (run with `rspec rspec_ruby_segfault.rb`), and the output I got when the error occurred.

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

* Author: Arne Brasseur
* Status: Open
* Priority: High
* Assignee: Koichi Sasada
* Category: YARV
* 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/