From: integ3rs@... Date: 2017-05-24T03:31:42+00:00 Subject: [ruby-core:81366] [Ruby trunk Bug#13596] Segfault when catching SystemStackError in eval Issue #13596 has been reported by mjones (Morgan Jones). ---------------------------------------- Bug #13596: Segfault when catching SystemStackError in eval https://bugs.ruby-lang.org/issues/13596 * Author: mjones (Morgan Jones) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux] * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- This minimal testcase will crash most ruby versions with a SIGSEGV (though it's likely that other constructions could trigger the same behavior): ~~~ ruby -e "code = '+1' * 100000; 2.times {begin; eval(code); rescue SystemStackError; end}" ~~~ It seems that the crash is triggered by attempting to access the stack redzone. -- https://bugs.ruby-lang.org/ Unsubscribe: