This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [PATCH]: natThread.cc: Destroy join sync objects in finalizer
- From: Tom Tromey <tromey at redhat dot com>
- To: gnustuff at thisiscool dot com
- Cc: Bryce McKinlay <mckinlay at redhat dot com>,Hans Boehm <Hans dot Boehm at hp dot com>,GCJ Patches <java-patches at gcc dot gnu dot org>
- Date: 12 Sep 2004 17:58:48 -0600
- Subject: Re: [PATCH]: natThread.cc: Destroy join sync objects in finalizer
- References: <ID61A5YUKGOMQKD8JG1V4WZA8TSKFB7.4144d1a9@p733>
- Reply-to: tromey at redhat dot com
>>>>> "Mohan" == Mohan Embar <gnustuff@thisiscool.com> writes:
Mohan> If someone decides to resurrect a thread this way instead of
Mohan> creating a thread pool, they're going to run into problems if
Mohan> they hope that they can rely on finalize() being called again
Mohan> the next time they feel like resurrecting a thread this way....
You can't re-start() a thread. My concern here is really about VM
security -- we don't want a way to, say, remote-crash a VM running in
a browser.
Tom