Date: Thu, 9 Sep 1999 10:16:30 -0600 From: Nate Williams <nate@mt.sri.com> To: SHUDO Kazuyuki <shudoh@muraoka.info.waseda.ac.jp> Cc: freebsd-java@FreeBSD.ORG Subject: Re: handling SIGQUIT Message-ID: <199909091616.KAA03489@mt.sri.com> In-Reply-To: <199909090437.NAA19986@cafe.muraoka.info.waseda.ac.jp> References: <199909090437.NAA19986@cafe.muraoka.info.waseda.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909091616.KAA03489>