[ruby-core:94454] [Ruby master Bug#10460] Segfault instead of stack level too deep
From:
merch-redmine@...
Date:
2019-08-21 03:52:37 UTC
List:
ruby-core #94454
Issue #10460 has been updated by jeremyevans0 (Jeremy Evans). Status changed from Open to Closed This appears to have been fixed between 2.4 and 2.5, as the example no longer has a segfault on 2.5, 2.6, 2.7.0-preview1, or the master branch. ---------------------------------------- Bug #10460: Segfault instead of stack level too deep https://bugs.ruby-lang.org/issues/10460#change-80885 * Author: plexus (Arne Brasseur) * Status: Closed * Priority: Normal * Assignee: nobu (Nobuyoshi Nakada) * Target version: * 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/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>