This is the mail archive of the
java-prs@sources.redhat.com
mailing list for the Java project.
Re: libgcj/289
- To: tromey at cygnus dot com
- Subject: Re: libgcj/289
- From: Tom Tromey <tromey at cygnus dot com>
- Date: 13 Sep 2000 15:00:00 -0000
- Cc: java-prs at sourceware dot cygnus dot com,
- Reply-To: Tom Tromey <tromey at cygnus dot com>
The following reply was made to PR libgcj/289; it has been noted by GNATS.
From: Tom Tromey <tromey@cygnus.com>
To: Bryce McKinlay <bryce@albatross.co.nz>
Cc: java-gnats@sourceware.cygnus.com
Subject: Re: libgcj/289
Date: 13 Sep 2000 09:05:00 -0600
Bryce> Interesting. It seems that in the JDK, a join() on a thread
Bryce> that throws an unchecked exception never returns. This
Bryce> behaviour seems reasonable, I guess, as a thread that throws an
Bryce> exception could potentially leave objects in an unstable
Bryce> state. This is consistent across several different JDK versions
Bryce> (and combinations of green/native threads), so perhaps we
Bryce> should look at duplicating it.
This behavior seems broken to me. If I'm trying to join() a thread, I
probably don't care how the thread exited -- just that it did. If we
follow the Sun implementation then a join() of an
abnormally-terminated thread will just cause the runtime to hang.
This seems losing.
Tom