From owner-freebsd-java@FreeBSD.ORG Tue Dec 6 23:16:17 2005 Return-Path: X-Original-To: freebsd-java@freebsd.org Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB2AE16A41F; Tue, 6 Dec 2005 23:16:17 +0000 (GMT) (envelope-from freebsd@spatula.net) Received: from turing.morons.org (morons.org [64.147.161.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A67B43D55; Tue, 6 Dec 2005 23:16:17 +0000 (GMT) (envelope-from freebsd@spatula.net) Received: from localhost (localhost.morons.org [127.0.0.1]) by turing.morons.org (Postfix) with ESMTP id 218F3170DC; Tue, 6 Dec 2005 15:16:17 -0800 (PST) Received: from turing.morons.org ([127.0.0.1]) by localhost (turing.morons.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22025-08; Tue, 6 Dec 2005 15:16:16 -0800 (PST) Received: by turing.morons.org (Postfix, from userid 1001) id 2717417072; Tue, 6 Dec 2005 15:16:16 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by turing.morons.org (Postfix) with ESMTP id 2651E17071; Tue, 6 Dec 2005 15:16:16 -0800 (PST) Date: Tue, 6 Dec 2005 15:16:16 -0800 (PST) From: freebsd@spatula.net X-X-Sender: spatula@turing To: bug-followup@FreeBSD.org In-Reply-To: <20051206141650.O2752@turing> Message-ID: <20051206150709.U2752@turing> References: <20051206141650.O2752@turing> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at morons.org Cc: freebsd-java@freebsd.org Subject: Re: threads/84778: libpthread busy loop/hang with Java when handling signals and Runtime.exec X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 23:16:18 -0000 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/