From owner-freebsd-threads@FreeBSD.ORG  Wed Sep 21 19:10:14 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 353F916A41F
	for <freebsd-threads@hub.freebsd.org>;
	Wed, 21 Sep 2005 19:10:14 +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 C47FD43D48
	for <freebsd-threads@hub.freebsd.org>;
	Wed, 21 Sep 2005 19:10:13 +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 j8LJADjn062703
	for <freebsd-threads@freefall.freebsd.org>;
	Wed, 21 Sep 2005 19:10:13 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j8LJADGm062702;
	Wed, 21 Sep 2005 19:10:13 GMT (envelope-from gnats)
Date: Wed, 21 Sep 2005 19:10:13 GMT
Message-Id: <200509211910.j8LJADGm062702@freefall.freebsd.org>
To: freebsd-threads@FreeBSD.org
From: Daniel Eischen <deischen@freebsd.org>
Cc: 
Subject: Re: kern/86029: undefined reference to `_thread_dump_info'
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: Wed, 21 Sep 2005 19:10:14 -0000

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

From: Daniel Eischen <deischen@freebsd.org>
To: Christopher Sean Morrison <brlcad@mac.com>
Cc: David Xu <davidxu@freebsd.org>, <bug-followup@freebsd.org>
Subject: Re: kern/86029: undefined reference to `_thread_dump_info'
Date: Wed, 21 Sep 2005 15:07:16 -0400 (EDT)

 On Wed, 21 Sep 2005, Christopher Sean Morrison wrote:
 
 > On Sep 21, 2005, at 1:28 PM, Daniel Eischen wrote:
 >
 > > That's what SIGINFO is for.  Again, that's undocumented and
 > > allowed to change, but it's better than calling a library
 > > internal function.
 >
 > Again, this is really tangent to the whole point of the report, but it
 > does raise ab additional question.  If I raise a SIGINFO, is that going
 > to give identical detail about the current threading states?  I agree
 > that it's better means to the end.  The OpenBSD pthreads(3) manual page
 > does document the signal but I have not had a motivation to change/test
 > that bit of code until now.
 
 If you're debugging the threads library, you should be looking
 at its source.  SIGINFO just calls _thread_dump_info() (which
 is not exported in libpthread) and does the same thing.  But,
 SIGINFO was meant more for us to debug the thread library.
 
 > Which has always been my understanding of -pthread as well.  Does this
 > mean then that the C library routines on an AMD64 FreeBSD 5.4 system
 > are supposed to be re-entrant and thread safe?
 
 Of course.
 
 > If that's the case,
 > then I probably have another bug report to make.  It also doesn't
 > explain the inconsistency with the same rev of FreeBSD on IA32 systems
 > where the same behavior is not exhibited.
 
 I'm going to close this one.  You'll need something that
 easily regenerates your problem if you file another bug
 report on it.
 
 -- 
 DE