From owner-freebsd-java@FreeBSD.ORG Tue Dec 6 23:34:35 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 9130A16A448; Tue, 6 Dec 2005 23:34:35 +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 2561743D66; Tue, 6 Dec 2005 23:34:35 +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 D6A6A17058; Tue, 6 Dec 2005 15:34:34 -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 23238-01; Tue, 6 Dec 2005 15:34:32 -0800 (PST) Received: by turing.morons.org (Postfix, from userid 1001) id 845E617049; Tue, 6 Dec 2005 15:34:32 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by turing.morons.org (Postfix) with ESMTP id 8097217042; Tue, 6 Dec 2005 15:34:32 -0800 (PST) Date: Tue, 6 Dec 2005 15:34:32 -0800 (PST) From: freebsd@spatula.net X-X-Sender: spatula@turing To: bug-followup@FreeBSD.org In-Reply-To: <200512062320.jB6NK9RS075945@freefall.freebsd.org> Message-ID: <20051206153047.J2752@turing> References: <200512062320.jB6NK9RS075945@freefall.freebsd.org> 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:34:35 -0000 As I continue to muck about with this I'm finding a few new things out. I sent the process a ^Z, which caused the process to begin running away. Then I sent it a kill -stop and waited for the process to stop completely. Then I ran gcore, and although the first few stack frames are probably caused by the stop signal, the last stack frame may be telling: Cannot get thread info: generic error (gdb) bt #0 0x480a0090 in __error () from /usr/lib/libpthread.so.2 #1 0x4808d074 in sigaction () from /usr/lib/libpthread.so.2 #2 0x4808d624 in sigaction () from /usr/lib/libpthread.so.2 #3 0x48097bd0 in pthread_mutexattr_init () from /usr/lib/libpthread.so.2 #4 0x00000000 in ?? () Looks like sending a ^Z may be causing Java to dereference a null. I'll continue investigating to see what else can be discovered. -- "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/