From owner-freebsd-java  Wed Sep  8 21:42: 4 1999
Delivered-To: freebsd-java@freebsd.org
Received: from cafe.muraoka.info.waseda.ac.jp (cafe.muraoka.info.waseda.ac.jp [133.9.68.49])
	by hub.freebsd.org (Postfix) with ESMTP id E497C15158
	for <freebsd-java@FreeBSD.ORG>; Wed,  8 Sep 1999 21:41:30 -0700 (PDT)
	(envelope-from shudoh@muraoka.info.waseda.ac.jp)
Received: from muraoka.info.waseda.ac.jp (shudoh@localhost [127.0.0.1])
	by cafe.muraoka.info.waseda.ac.jp (8.9.1a/3.7W) with ESMTP id NAA19986
	for <freebsd-java@FreeBSD.ORG>; Thu, 9 Sep 1999 13:37:18 +0900
Message-Id: <199909090437.NAA19986@cafe.muraoka.info.waseda.ac.jp>
To: freebsd-java@FreeBSD.ORG
Subject: handling SIGQUIT
Date: Thu, 09 Sep 1999 13:37:18 +0900
From: SHUDO Kazuyuki <shudoh@muraoka.info.waseda.ac.jp>
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

I found the behavior of JDK 1.1.8 V99-7-19 which may be a bug.

While NetBeans (www.netbeans.com) 2.1.1 starting up I
send many SIGQUIT to the JDK by rapid hitting Control-\.
The JDK occasionally hang up with the following message:

  SIGQUIT   3*   quit

  Full thread dump:
      BOGUS-HANDLE[6d0049] (TID:0x290024a8, sys_thread_t:0x290024d8, state:6d0049?) prio=687875304
      BOGUS-HANDLE[690054] (TID:0x29000600, sys_thread_t:0x81d3400, state:81694d0?) prio=135698076Abort trap

Is signal handler called during handler is executed?

JDK 1.1.7 for Linux may have the same problem:

  SIGQUIT   3*   quit
          stackbase=0x2ef6a000, stackpointer=0x2ef69cf8

  *** panic: Internal error dumping threads!

JDK 1.2 pre-release 2 for Linux will not have the problem.

Kazuyuki SHUDO				Happy Hacking!
  Muraoka Lab., Grad. School of Sci. & Eng., Waseda Univ.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-java" in the body of the message