[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cp-patches] fix JAWT self-deadlock
From: |
Thomas Fitzsimmons |
Subject: |
[cp-patches] fix JAWT self-deadlock |
Date: |
Tue, 13 Sep 2005 15:00:30 -0400 |
Hi,
Some JAWT-using demos were self-deadlocking on the GDK lock. I've
removed the gdk_threads_enter and gdk_threads_leave calls from
_Jv_AWTLock and _Jv_AWTUnlock. I'm not sure what these functions are
meant to do so I've just left FIXME comments for now.
Tom
2005-09-13 Thomas Fitzsimmons <address@hidden>
* native/jawt/jawt.c (_Jv_AWTLock): Do nothing.
(_Jv_AWTUnlock): Likewise.
Index: native/jawt/jawt.c
===================================================================
RCS file: /cvsroot/classpath/classpath/native/jawt/jawt.c,v
retrieving revision 1.2
diff -u -r1.2 jawt.c
--- native/jawt/jawt.c 20 Aug 2005 22:46:54 -0000 1.2
+++ native/jawt/jawt.c 13 Sep 2005 18:53:36 -0000
@@ -176,11 +176,11 @@
static void
(JNICALL _Jv_AWTLock) (JNIEnv* env __attribute__((unused)))
{
- classpath_jawt_lock ();
+ /* FIXME: what is this supposed to do? */
}
static void
(JNICALL _Jv_AWTUnlock) (JNIEnv* env __attribute__((unused)))
{
- classpath_jawt_unlock ();
+ /* FIXME: what is this supposed to do? */
}
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [cp-patches] fix JAWT self-deadlock,
Thomas Fitzsimmons <=