[MacRuby] #203: Marshal.dump does not serialize an Exception's backtrace

MacRuby ruby-noreply at macosforge.org
Sat Dec 4 09:16:41 PST 2010


#203: Marshal.dump does not serialize an Exception's backtrace
----------------------------------------+-----------------------------------
 Reporter:  vincent.isambart@…          |       Owner:  lsansonetti@…        
     Type:  defect                      |      Status:  new                  
 Priority:  major                       |   Milestone:                       
Component:  MacRuby                     |    Keywords:                       
----------------------------------------+-----------------------------------

Comment(by jhemmelg@…):

 I have been looking into this bug.  I have traced the cause to not
 marshalling out ivars.  It looks like this is at least partially due to
 the fact that strings are UTF-8 only (ticket #742).  When I change
 Marshal's w_object() to output ivars it hits an infinite loop marshalling
 out the string.  When a string is marshalled out, it's encoding is
 marhsalled out as well.  The string encoding is a string itself.  When
 that string is marshalled out, it's encoding is marshalled as well.  It's
 turtles all the way down until the stack blows up.  In MatzRuby there is a
 short circuit for US-ASCII and UTF-8 that breaks this recursion.

 I think we need to resolve handling string encodings (ticket #742) before
 this bug can be fixed.  I also think this needs to be a 1.0 bug.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/203#comment:1>
MacRuby <http://macruby.org/>



More information about the macruby-tickets mailing list