Issue #9198 has been updated by Eric Wong.


 Does it go away if you wrap the test with Thread.new?
 Likely the same problem I describe in [ruby-core:60248]
 
 --- a/test/ruby/test_exception.rb
 +++ b/test/ruby/test_exception.rb
 @@ -480,10 +480,12 @@ def test_stackoverflow
    def test_machine_stackoverflow
      bug9109 = '[ruby-dev:47804] [Bug #9109]'
      assert_separately([], <<-SRC)
 +    Thread.new do
      assert_raise(SystemStackError, #{bug9109.dump}) {
        h = {a: ->{h[:a].call}}
        h[:a].call
      }
 +    end
      SRC
    rescue SystemStackError
    end

----------------------------------------
Bug #9198: Segfault in TestException#test_machine_stackoverflow
https://bugs.ruby-lang.org/issues/9198#change-44822

* Author: Vit Ondruch
* Status: Open
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: ruby 2.1.0dev (2013-11-23 trunk 43807) [x86_64-linux]
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN
----------------------------------------
I observe segfault in TestException#test_machine_stackoverflow test case for -preview2. Please see attached log.

---Files--------------------------------
segfault.log (830 KB)


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