Issue #14279 has been updated by ko1 (Koichi Sasada). > I think something like a TypeError should be raised in such a case. ```ruby a = 13 p(*a) #=> 13 ``` So that this case is similar to `super(13)`. Ruby 2.2 to 2.5 have same issue. Thank you for your report. ---------------------------------------- Bug #14279: Modifying splat argument causes segmentation fault https://bugs.ruby-lang.org/issues/14279#change-69209 * 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: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- 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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>