Unexpected Hash Modification and Segmentation Fault with Named Arguments
|ruby -v:||ruby 2.1.2p95 (2014-05-08 revision 45877) [i686-linux]
||Backport:||2.0.0: DONTNEED, 2.1: DONE
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.
merge revision(s) r46342: [Backport #9954]
* vm.c (core_hash_merge_kwd): should return the result hash, which
may be converted from and differ from the given argument.
- Duplicates Bug #9898: Keyword argument oddities added
- Status changed from Open to Closed
- Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN to 2.0.0: DONTNEED, 2.1: REQUIRED
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.
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.
- Backport changed from 2.0.0: DONTNEED, 2.1: REQUIRED to 2.0.0: DONTNEED, 2.1: DONE
ruby_2_1 branch at r46619.
Also available in: Atom