Bug #7627

Instance variables of a Struct object are marshaled even when marshal_dump method is defined.

Added by Kirill Lashuk over 1 year ago. Updated about 1 year ago.

[ruby-core:51163]
Status:Closed
Priority:Normal
Assignee:-
Category:-
Target version:-
ruby -v:ruby 2.0.0dev (2012-11-01 trunk 37411) [x86_64-darwin12.2.0] Backport:

Description

=begin
If (({marshaldump})) method is defined in a class and you pass an instance of that class into (({Marshal.dump})), instead of dumping instance variables (as it happens by default, when (({marshaldump})) is not defined) Ruby dumps only data returned from this method.

Though, if the class is a (({Struct})), MRI 1.8.7 behaves the same way as for a regular class, but both MRI 1.9.3 and MRI 2.0.0 in addition to the data returned from (({marshal_dump})) method automatically dump instance variables of the object.

Code example:

# marshal.rb

class A
attr_accessor :foo

def marshaldump; 'dump'; end # fake dump data
def marshal
load(*); end # do nothing
end

class B < Struct.new(:bar)
attr_accessor :foo

def marshaldump; 'dump'; end # fake dump data
def marshal
load(*); end # do nothing
end

def test(obj)
obj.foo = 12

dump = Marshal.dump(obj)
loaded = Marshal.load(dump)

p obj, dump, loaded, loaded.foo
puts
end

test(A.new)
test(B.new)

MRI 1.8.7 (instance variable of the Struct object ((is not dumped))):

$ ruby-1.8.7-p371 marshal.rb
#
"\004\bU:\006A\"\tdump"
#
nil

#
"\004\bIU:\006B\"\tdump\000"
#
nil

MRI 1.9.3 (instance variable of the Struct object ((is dumped))):

$ ruby-1.9.3-p327 marshal.rb
#
"\x04\bU:\x06AI\"\tdump\x06:\x06EF"
#
nil

#
"\x04\bIU:\x06BI\"\tdump\x06:\x06EF\x06:\t@fooi\x11"
#
12

MRI 2.0.0-preview1 (instance variable of the Struct object ((is dumped))):

$ ruby-2.0.0-preview1 marshal.rb
#
"\x04\bU:\x06AI\"\tdump\x06:\x06EF"
#
nil

#
"\x04\bIU:\x06BI\"\tdump\x06:\x06EF\x06:\t@fooi\x11"
#
12

I'm not sure if it's expected behavior, but it doesn't look like one to me. Probably, it has something to do with the implementation of (({hasivars})) macro that for some reason is used (()) while dumping an object with defined (({marshaldump})) method, but I might be wrong, because I didn't manage to track down the problem further.

=end

Associated revisions

Revision 38952
Added by Nobuyoshi Nakada about 1 year ago

marshal.c: marshal_dump instance varialbes

  • marshal.c (wobject): dump instance varialbes of the result of marshaldump not the original object. [Bug #7627]
  • complex.c (nucompmarshaldump): need to copy instance variables.
  • rational.c (nuratmarshaldump): ditto.

Revision 40392
Added by Nobuyoshi Nakada about 1 year ago

marshal.c: use ivars of marshal_dump data

  • marshal.c (wobject): dump no ivars to the original by marshaldump. [Bug #8276]
  • marshal.c (robject0): copy all ivars of marshaldump data to the result object instead. [Bug #7627]

Revision 40408
Added by Nobuyoshi Nakada 12 months ago

marshal.c: fix marshal_load ivar

  • marshal.c (r_object0): copy all instance variables not only generic ivars, before calling post proc. [Bug #7627]

History

#1 Updated by Koichi Sasada about 1 year ago

I'm not sure about this issue, but is it high-priority trunk issue?
or not important issue?

#2 Updated by Nobuyoshi Nakada about 1 year ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

This issue was solved with changeset r38952.
Kirill, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.


marshal.c: marshal_dump instance varialbes

  • marshal.c (wobject): dump instance varialbes of the result of marshaldump not the original object. [Bug #7627]
  • complex.c (nucompmarshaldump): need to copy instance variables.
  • rational.c (nuratmarshaldump): ditto.

Also available in: Atom PDF