This is the mail archive of the
mailing list for the Java project.
Re: Is serialization broken?
- To: Warren Levy <warrenl at redhat dot com>
- Subject: Re: Is serialization broken?
- From: Bryce McKinlay <bryce at albatross dot co dot nz>
- Date: Sat, 27 Jan 2001 13:53:16 +1300
- CC: Barnet Wagman <wagman at enteract dot com>, "java-discuss at sources dot redhat dot com" <java-discuss at sources dot redhat dot com>
- References: <Pine.LNX.email@example.com>
Warren Levy wrote:
> On Fri, 26 Jan 2001, Barnet Wagman wrote:
> > I'm getting an erroneous ClassCastException deserializing an object with
> > gcj, gcc version 2.97 20010117 (experimental).
> > With the test program SerTest.java (below)...
> Well, it seems that java.io.DataInputStream.readInt is throwing an
> EOFException because it is mistakenly reading some negative data to mean
> EOF. I was able to jump past the check for the negative value in the
> debugger and the program ran to completion just fine.
Ouch. Now that I look at this, my DataInputStream patch from classpath should
go in. It will re-merge the implementations and ought to fix this bug.
> Breakpoint 2, java.util.HashMap.readObject (this=@8101fc8, s=@8086400)
> at /home/warrenl/egcs/libjava/java/util/HashMap.java:639
> 639 s.defaultReadObject();
Hmm... do you have a magic GDB that can demange new-ABI java symbols? I'm
using the latest gdb from cvs, which seems to work quite nicely, but it
doesn't demangle. I was planning to make an attempt to fix this, but don't
want to duplicate someone elses effort.
[ bryce ]