This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: Problems with libjava's AWT
- From: Tom Tromey <tromey at redhat dot com>
- To: Bryce McKinlay <mckinlay at redhat dot com>
- Cc: Bernd Schmidt <bernds at btinternet dot com>, java at gcc dot gnu dot org,java-patches at gcc dot gnu dot org
- Date: 16 Jun 2004 16:01:42 -0600
- Subject: Re: Problems with libjava's AWT
- References: <Pine.LNX.4.58.0406061352490.6420@tesuji.local><40D09B9B.60306@redhat.com>
- Reply-to: tromey at redhat dot com
Bryce> Nope. wait() implicitly releases the lock when the wait begins, and
Bryce> reaquires it before returning. I don't think there is a deadlock here.
I agree -- in fact, you're required to synchronize on an object before
you can wait() or notify() on it.
Tom