From owner-freebsd-threads@FreeBSD.ORG Tue Dec 6 23:40:21 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 A3E4F16A41F for ; Tue, 6 Dec 2005 23:40:21 +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 B060E43D88 for ; Tue, 6 Dec 2005 23:40:06 +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 jB6Ne6GO077801 for ; Tue, 6 Dec 2005 23:40:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jB6Ne604077800; Tue, 6 Dec 2005 23:40:06 GMT (envelope-from gnats) Date: Tue, 6 Dec 2005 23:40:06 GMT Message-Id: <200512062340.jB6Ne604077800@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:40:21 -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:34:32 -0800 (PST) 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/