From: johncbackus@...
Date: 2017-05-12T07:54:12+00:00
Subject: [ruby-core:81124] [Ruby trunk Bug#10290] segfault when calling a lambda recursively after rescuing SystemStackError

Issue #10290 has been updated by backus (John Backus).


nobu (Nobuyoshi Nakada) wrote:
> On macOS, `--with-setjmp-type=setjmp` configuration option may fix it.

This does fix the issue on macOS for me, thank you. Maybe this should be the macOS default? 

----------------------------------------
Bug #10290: segfault when calling a lambda recursively after rescuing SystemStackError
https://bugs.ruby-lang.org/issues/10290#change-64775

* Author: jacknagel (Jack Nagel)
* Status: Assigned
* Priority: Normal
* Assignee: nobu (Nobuyoshi Nakada)
* Target version: 
* ruby -v: ruby 2.1.3p242 (2014-09-19 revision 47629) [x86_64-darwin13.0]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
The following code segfaults on Ruby 2.1.3:

```ruby
l = -> { l.() }

begin
  l.()
rescue SystemStackError
  l.() # segfault
end
```

the issue does not occur on trunk.

---Files--------------------------------
ruby_2014-09-25-000925_haswell.log (46.4 KB)
ruby_2014-09-25-001644_haswell.log (46.8 KB)


-- 
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>