From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30875 invoked by alias); 15 May 2007 09:46:02 -0000 Received: (qmail 30855 invoked by uid 48); 15 May 2007 09:46:01 -0000 Date: Tue, 15 May 2007 09:46:00 -0000 Message-ID: <20070515094601.30854.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libgcj/16662] IllegalMonitorStateException in EventQueue.getNextEvent(): possible hash synchronization bug? In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: java-prs@gcc.gnu.org From: "rob1weld at aol dot com" Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org X-SW-Source: 2007-q2/txt/msg00085.txt.bz2 ------- Comment #11 from rob1weld at aol dot com 2007-05-15 10:46 ------- Here are my results with "gcc version 4.2.0 20070505 (prerelease)". /wonka# ./vte logMessage is called /root/downloads/gcc-4_2-branch/libjava/classpath/native/jni/gtk-peer/gthread-jni.c:1242: AWT JNI failure (BROKEN): cannot exit monitor Description follows to System.err: java.lang.IllegalMonitorStateException: current thread not owner <> /root/downloads/gcc-4_2-branch/libjava/classpath/native/jni/gtk-peer/gthread-jni.c:1242: Aborting execution; BROKEN: cannot exit monitor Aborting execution Aborted I tried to chose "reopen bug" but that is not allowed (for me). I will file a new report and reference this bug. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16662