This is the mail archive of the java@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: jogl deadlock

From: Anthony Green <green at redhat dot com>
To: tromey at redhat dot com
Cc: Thomas Fitzsimmons <fitzsim at redhat dot com>, java at gcc dot gnu dot org
Date: Tue, 17 May 2005 09:11:22 -0700
Subject: Re: jogl deadlock
References: <1116344222.4756.17.camel@localhost.localdomain> <m3br79svel.fsf@localhost.localdomain>

On Tue, 2005-05-17 at 09:51 -0600, Tom Tromey wrote:
> Could you use gdb and see how it is deadlocking?  What it is waiting
> for?

I tried that earlier, and one of the thread stack traces was completely
botched.  I think it must have been the AWT event thread (that's a
separate thread, right?).

AG

References:
- jogl deadlock
  - From: Anthony Green
- Re: jogl deadlock
  - From: Tom Tromey

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