From owner-freebsd-threads@FreeBSD.ORG Tue Dec 6 23:20:19 2005 Return-Path: X-Original-To: freebsd-threads@hub.freebsd.org Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF67716A41F for ; Tue, 6 Dec 2005 23:20:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5674543D77 for ; Tue, 6 Dec 2005 23:20:15 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB6NK9x0075946 for ; Tue, 6 Dec 2005 23:20:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jB6NK9RS075945; Tue, 6 Dec 2005 23:20:09 GMT (envelope-from gnats) Date: Tue, 6 Dec 2005 23:20:09 GMT Message-Id: <200512062320.jB6NK9RS075945@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: freebsd@spatula.net Cc: Subject: Re: threads/84778: libpthread busy loop/hang with Java when handling signals and Runtime.exec X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@spatula.net List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 23:20:19 -0000 The following reply was made to PR threads/84778; it has been noted by GNATS. From: freebsd@spatula.net To: bug-followup@FreeBSD.org Cc: freebsd-java@freebsd.org Subject: Re: threads/84778: libpthread busy loop/hang with Java when handling signals and Runtime.exec Date: Tue, 6 Dec 2005 15:16:16 -0800 (PST) Another bit of information of interest: sending the process a kill -stop (-17) after trying to stop it with ^Z *will* cause the process to stop. Sending it a kill -stop without hitting ^Z will also cause the process to stop normally. In either case, however, resuming from the shell with fg will cause the same infinite-loop behaviour. Resuming with a kill -19 will also cause the infinite-loop behaviour. Sending a regular kill signal also causes the infinite-loop behaviour. The process has to be killed with a kill -9 in all cases once this behaiour starts. -- "The aptly-named morons.org is an obscenity-laced screed..." -- Robert P. Lockwood, Catholic League director of research Nick Johnson, version 2.1 http://web.morons.org/