--- a/test/java/io/Serializable/6559775/README Mon Oct 18 15:35:14 2010 -0700+++ /dev/null Thu Jan 01 00:00:00 1970 +0000@@ -1,29 +0,0 @@-The testcase works well on dual core machines.-The below output indicates a successful fix:--Exception in thread "Thread-0" java.lang.NullPointerException- at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:476)- at SerialRace$1.run(SerialRace.java:33)- at java.lang.Thread.run(Thread.java:595)---When the vulnerability exists, the output of the tescase is something like this:-Available processors: 2-Iteration 1-java.io.NotActiveException: not in readObject invocation or fields already read- at java.io.ObjectInputStream$CallbackContext.checkAndSetUsed(ObjectInputStream.java:3437)- at java.io.ObjectInputStream$CallbackContext.getObj(ObjectInputStream.java:3427)- at java.io.ObjectInputStream.readFields(ObjectInputStream.java:514)- at SerialVictim.readObject(SerialVictim.java:19)- at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)- at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)- at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)- at java.lang.reflect.Method.invoke(Method.java:585)- at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)- at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)- at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)- at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)- at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)- at SerialRace.main(SerialRace.java:65)-Victim: ?-Victim: $

--- a/test/java/io/Serializable/6966692/README Mon Oct 18 15:35:14 2010 -0700+++ /dev/null Thu Jan 01 00:00:00 1970 +0000@@ -1,23 +0,0 @@-Testcase shows default deserialisation of the Victim having two values for the same field. --Probably requires dual core to run successfully. --Reading thread is warmed up so that it can easily win the race for the demonstration, but this means we need to make the field volatile.--Typical output:--Victim@1551f60 BBBB-Victim@1551f60 AAAA--The output when its fixed is, -Victim@1975b59 AAAA-Victim@1975b59 AAAA - The value is retained--and when it is not fixed, it shows something like -Victim@173a10f AAAA-Victim@173a10f BBBB - the value of the object gets set again and hence is different. This is a bug--Look at the -AAAA AAAA -and -AAAA BBBB