From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2169 invoked by alias); 11 Mar 2006 19:07:27 -0000 Received: (qmail 2153 invoked by uid 22791); 11 Mar 2006 19:07:26 -0000 X-Spam-Check-By: sourceware.org Received: from 62-177-154-238.static.bbeyond.nl (HELO lembu.sumatrasoftware.com) (62.177.154.238) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 11 Mar 2006 19:07:23 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: runFinalization in Classloader.initialize doesn't run on cacao Date: Sat, 11 Mar 2006 19:07:00 -0000 Message-ID: From: "Jeroen Frijters" To: "Olivier Jolly" Cc: , "Mauve Patch List" X-IsSubscribed: yes Mailing-List: contact mauve-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00058.txt.bz2 Olivier Jolly wrote: > while wandering around with Classloaders, I found that the teslet > gnu.testlet.java.lang.Classloader.initialize wasn't running=20 > with Cacao. > It seems that in the beginning of the test method, it creates an > anonymous Classloader and then call System.gc() and > System.runFinalization() and expects the finalizer to be ran to set a > singleton like variable holder. > While this is ok in jamvm and sun jre 1.5.0, cacao doesn't run the > finalizer since runFinalization only gives a hint and not a mandatory > order, so it is compliant. > My question is whether I'm missing something and this way of doing > brings something in this test or it could be rewritten in a=20 > simpler way, more compliant with the various jvm. I'm obviously not aware of an easier (or more robust) way to do this, or I would have used it. However, this is a very important test (from a security pov), so it has to be in. If Cacao can't or won't support System.runFinalization(), I suggest skipping this test. Regards, Jeroen