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: Thomas Fitzsimmons <fitzsim at redhat dot com>
Cc: java at gcc dot gnu dot org
Date: Tue, 17 May 2005 10:10:43 -0700
Subject: Re: jogl deadlock
References: <1116344222.4756.17.camel@localhost.localdomain> <1116344831.689.8.camel@tortoise.toronto.redhat.com> <1116346343.4756.22.camel@localhost.localdomain> <1116349081.4347.1.camel@tortoise.toronto.redhat.com>

On Tue, 2005-05-17 at 12:58 -0400, Thomas Fitzsimmons wrote:
> In jni/gtk-peer/gtkpeer.h change:
> 
> #define DEBUG_LOCKING 0
> 
> to
> 
> #define DEBUG_LOCKING 1
> 
> and rebuild the peers.

Thanks.  Is it reasonable to consider turning this into a system
property?  This isn't the first time I've had to do this to debug some
problem.

AG

References:
- jogl deadlock
  - From: Anthony Green
- Re: jogl deadlock
  - From: Thomas Fitzsimmons
- Re: jogl deadlock
  - From: Anthony Green
- Re: jogl deadlock
  - From: Thomas Fitzsimmons

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