>> The implementation of ObjectInputStream.readObject() in this version >> of libgcj calls the constructor of the serialize object it is reading. >> Sun's implementation does not do this, nor (I think) did earlier >> versions of libgcj. Below is a sample program which prints "foo" once >> with javac, but twice with gcj/libgcj.
This bug also exists in the gcj CVS trunk. I've written a patch which I am testing. I will check it in as soon as I'm satisfied with it. The fix will appear in gcj 3.1. Tom