Issue #9589 has been updated by Cezary Baginski.


Not sure if it's related, but I'm getting segfaults instead of SystemStackErrors with recursive lambda calls from:

example_spec.rb:

`describe Fixnum do
  subject { subject }
  it { should be }
end`

by running: 

`rspec example_spec.rb`

using this version of rspec:

`rspec (2.14.1)
rspec-core (2.14.8)`

Both on:

`ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-linux]`

and:

`ruby 2.2.0dev (2014-03-04 trunk 45264) [x86_64-linux]`


but the debug build of 2.2.0 (-O0 and -ggdb3) gives SystemStackError as expected.

(all examples compiled with gcc (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3)

----------------------------------------
Bug #9589: Stack level too deep during eval causes segmentation fault
https://bugs.ruby-lang.org/issues/9589#change-45608

* Author: carlos aya
* Status: Open
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
The following silly code, which imho should generate a " stack level too deep (SystemStackError)", segfaults

$ echo 'eval($_)' | ruby -n -e 'eval($_)'

I thought it may be a bug, not sure.

My version:
carlos-mac$ ruby -v
ruby 1.9.3p327 (2012-11-10) [x86_64-darwin12.2.0]





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