This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug java/11209] New: Problems with the reset method in ObjectOutputStream.
- From: "daj2 at cs dot wustl dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 Jun 2003 15:06:42 -0000
- Subject: [Bug java/11209] New: Problems with the reset method in ObjectOutputStream.
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11209
Summary: Problems with the reset method in ObjectOutputStream.
Product: gcc
Version: 3.2.2
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: java
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: daj2@cs.wustl.edu
CC: gcc-bugs@gcc.gnu.org
The research group I am working with is working on compiling some AspectJ based reference
counting with GCJ. However we are running into problems with recycling objects and then
writing them across an ObjectOutputStream. Specifically, values in recycled objects on
client-side are inconsistent with the correct values on server-side, where the recycling takes
place. Is there a problem with the reset method that causes it to not reread a value from
memory after reset it called? We have tracked this error and are certain that the values prior
to the write out are correct.