From: nagachika00@... Date: 2018-01-05T05:41:31+00:00 Subject: [ruby-core:84636] [Ruby trunk Bug#14279] Modifying splat argument causes segmentation fault Issue #14279 has been updated by nagachika (Tomoyuki Chikanaga). Backport changed from 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN to 2.3: REQUIRED, 2.4: REQUIRED, 2.5: REQUIRED Though I cannot reproduce SEGV on my box with any version of ruby (2.2.6, 2.4.6, 2.4.3, 2.5.0), I believe reporter's and ko1's statement and set Backport field. :p ---------------------------------------- Bug #14279: Modifying splat argument causes segmentation fault https://bugs.ruby-lang.org/issues/14279#change-69211 * Author: coreycerovsek (Corey Cerovsek) * Status: Closed * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.5.0rc1 (2017-12-14 trunk 61243) [x86_64-linux] * Backport: 2.3: REQUIRED, 2.4: REQUIRED, 2.5: REQUIRED ---------------------------------------- Using Docker Ruby images ruby:2.2 through ruby:rc as of 2018-01-03, this little bit of code causes a segmentation fault: ~~~ class A def x(*args) args = 13 super end end A.new.x ~~~ I'm not sure what the behavior of super ought to be here, and it doesn't seem to be addressed by The Ruby Spec Suite, but with Ruby 2.1 (Docker ruby:2.1) this causes a "no superclass method" exception rather than crashing the interpreter. I'm guessing this has to do with the optimization in https://bugs.ruby-lang.org/issues/10440 -- https://bugs.ruby-lang.org/ Unsubscribe: