Bug #9954

Unexpected Hash Modification and Segmentation Fault with Named Arguments

Added by Andrew M 9 months ago. Updated 8 months ago.

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

Description

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.

segfault.rb Magnifier - File which reproduces the problem (1.2 KB) Andrew M, 06/18/2014 04:32 PM

pry_sample_output.txt Magnifier - Sample output my console (with PRY) (35 KB) Andrew M, 06/18/2014 04:36 PM

Related issues

Duplicates Ruby trunk - Bug #9898: Keyword argument oddities Closed 06/03/2014

Associated revisions

Revision 46619
Added by Tomoyuki Chikanaga 8 months ago

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.
   [Bug #9898]

History

#1 Updated by Nobuyoshi Nakada 9 months ago

  • Duplicates Bug #9898: Keyword argument oddities added

#2 Updated by Nobuyoshi Nakada 9 months ago

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

#3 Updated by Andrew M 9 months ago

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.

#4 Updated by Nobuyoshi Nakada 9 months ago

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.

#5 Updated by Tomoyuki Chikanaga 8 months ago

  • 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.

Also available in: Atom PDF