From owner-freebsd-java Thu Sep 9 9:17:33 1999 Delivered-To: freebsd-java@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 13232152B3 for ; Thu, 9 Sep 1999 09:17:15 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id KAA13809; Thu, 9 Sep 1999 10:16:31 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA03489; Thu, 9 Sep 1999 10:16:30 -0600 Date: Thu, 9 Sep 1999 10:16:30 -0600 Message-Id: <199909091616.KAA03489@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: SHUDO Kazuyuki Cc: freebsd-java@FreeBSD.ORG Subject: Re: handling SIGQUIT In-Reply-To: <199909090437.NAA19986@cafe.muraoka.info.waseda.ac.jp> References: <199909090437.NAA19986@cafe.muraoka.info.waseda.ac.jp> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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? I don't quite follow. Are you saying that SIGQUIT is being called during the SIGQUIT handler (causing a recursive error), or that the JDK should ignore SIGQUIT? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message