Bug #9954: Unexpected Hash Modification and Segmentation Fault with Named Arguments

• Status: Closed
• Priority: Normal
• Assignee: -
• Target version: 2.2.0
• ruby -v: ruby 2.1.2p95 (2014-05-08 revision 45877) [i686-linux]
• Backport: 2.0.0: DONTNEED, 2.1: DONE

[Ajedi32 (Andrew M)]

While experimenting with named arguments in Ruby 2.1.2, I encountered some strange behavior where a hash was modified after being passed as a set of named arguments with the double-splat operator. While attempting to examine the issue further, I encountered a segmentation fault which I believe to be related.

I have attached a log of my experiment, and a .rb file which reproduces both the unexpected hash modification and the segfault.

[nobu (Nobuyoshi Nakada)]

• Is duplicate of Bug #9898: Keyword argument oddities added

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed
• Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN to 2.0.0: DONTNEED, 2.1: REQUIRED

[Ajedi32 (Andrew M)]

Hmm... that doesn't really seem like the same issue (it has totally different symptoms from what I described here) but I'll trust your judgement on this one.

[nobu (Nobuyoshi Nakada)]

2.1.2p132 segfaults by your script, due to the access to the non-Hash object as a Hash object.
r46342 fixes it to return the converted result.

[nagachika (Tomoyuki Chikanaga)]

• Backport changed from 2.0.0: DONTNEED, 2.1: REQUIRED to 2.0.0: DONTNEED, 2.1: DONE

Backported into ruby_2_1 branch at r46619.