From owner-freebsd-threads@FreeBSD.ORG  Thu Oct  6 23:00:23 2005
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
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 866AE16A41F
	for <freebsd-threads@hub.freebsd.org>;
	Thu,  6 Oct 2005 23:00:23 +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 442DF43D46
	for <freebsd-threads@hub.freebsd.org>;
	Thu,  6 Oct 2005 23:00:23 +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 j96N0NO2042264
	for <freebsd-threads@freefall.freebsd.org>; Thu, 6 Oct 2005 23:00:23 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j96N0NXL042263;
	Thu, 6 Oct 2005 23:00:23 GMT (envelope-from gnats)
Date: Thu, 6 Oct 2005 23:00:23 GMT
Message-Id: <200510062300.j96N0NXL042263@freefall.freebsd.org>
To: freebsd-threads@FreeBSD.org
From: Daniel Eischen <deischen@freebsd.org>
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: Daniel Eischen <deischen@freebsd.org>
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2005 23:00:23 -0000

The following reply was made to PR threads/84778; it has been noted by GNATS.

From: Daniel Eischen <deischen@freebsd.org>
To: freebsd@spatula.net
Cc: bug-followup@freebsd.org
Subject: Re: threads/84778: libpthread busy loop/hang with Java when handling
 signals and Runtime.exec
Date: Thu, 6 Oct 2005 18:59:14 -0400 (EDT)

 On Thu, 6 Oct 2005 freebsd@spatula.net wrote:
 
 > select, however, does call nanosleep, and nanosleep does call
 > _nanosleep... but you're right that everything after that looks broken...
 > though I've never seen a stack get smashed like that before.  Usually I've
 > seen freakish addresses and "??" for function names, not addresses that
 > look reasonable and function names with symbols that can be actually
 > located.
 >
 > What happens when you gcore a running threaded process?  Do the process's
 > threads stop while the core dump is being written?  If not, could the
 > stack have changed while the core was being dumped and we're actually
 > seeing bits of stack from multiple running threads (and therefore
 > basically useless information)?
 
 I have no idea what or how gcore works.
 
 > Which thread do you see in a core dump if there are multiple threads?
 
 I don't know.  I've only ever used gdb on running processes.
 
 -- 
 DE