From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13744 invoked by alias); 26 Feb 2005 01:35:06 -0000 Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org Received: (qmail 13726 invoked by uid 48); 26 Feb 2005 01:35:05 -0000 Date: Mon, 28 Feb 2005 13:08:00 -0000 Message-ID: <20050226013505.13725.qmail@sourceware.org> From: "bonniot at users dot sf dot net" To: java-prs@gcc.gnu.org In-Reply-To: <20050223152937.20169.bonniot@users.sf.net> References: <20050223152937.20169.bonniot@users.sf.net> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libgcj/20169] Serialization: readResolve does not work X-Bugzilla-Reason: CC X-SW-Source: 2005-q1/txt/msg00533.txt.bz2 List-Id: ------- Additional Comments From bonniot at users dot sf dot net 2005-02-26 01:35 ------- After some investigation, I think I understand what is going wrong. It seems like readResolve is only called if it is declared in the deserialized object's class. However, it should also be searched for in the classes's parents, provided the method there is visible (that is, normal rules apply). I submitted a related testcase to mauve: http://sources.redhat.com/ml/mauve-patches/2005/msg00032.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20169