This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH]: natThread.cc: Destroy join sync objects in finalizer

From: Bryce McKinlay <mckinlay at redhat dot com>
To: tromey at redhat dot com
Cc: gnustuff at thisiscool dot com, GCJ Patches <java-patches at gcc dot gnu dot org>
Date: Sat, 11 Sep 2004 18:45:09 -0400
Subject: Re: [PATCH]: natThread.cc: Destroy join sync objects in finalizer
References: <FDGDIDTMIWSTR2WA7YV6Z6Z0XRONP.4141a31d@p733> <m3ekl8u224.fsf@localhost.localdomain>

Tom Tromey wrote:

Mohan> The GC finalizer finalize_native in natThread.cc should destroy
Mohan> the join synchronization objects if the target platform supports
Mohan> these destruction operations (which isn't the case for Linux and
Mohan> -DLINUX_THREADS but is the case for Win32).
This isn't a problem with your patch, but what happens if a user writes a subclass of Thread that has a finalize method which resurrects the Thread? Won't we start referring to freed data in this code?

Does the GC run finalizers in the order that they are registered? If so then we should be ok.

Bryce

Follow-Ups:
- Re: [PATCH]: natThread.cc: Destroy join sync objects in finalizer
  - From: Bryce McKinlay

References:
- [PATCH]: natThread.cc: Destroy join sync objects in finalizer
  - From: Mohan Embar
- Re: [PATCH]: natThread.cc: Destroy join sync objects in finalizer
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]