From owner-freebsd-threads@FreeBSD.ORG Thu Sep 22 12:20:08 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 58C9D16A41F for ; Thu, 22 Sep 2005 12:20:08 +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 3190243D5F for ; Thu, 22 Sep 2005 12:20:04 +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 j8MCK41J093927 for ; Thu, 22 Sep 2005 12:20:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j8MCK4gZ093925; Thu, 22 Sep 2005 12:20:04 GMT (envelope-from gnats) Date: Thu, 22 Sep 2005 12:20:04 GMT Message-Id: <200509221220.j8MCK4gZ093925@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: Christopher Sean Morrison 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: Christopher Sean Morrison List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2005 12:20:08 -0000 The following reply was made to PR kern/86029; it has been noted by GNATS. From: Christopher Sean Morrison To: Daniel Eischen Cc: David Xu , bug-followup@freebsd.org Subject: Re: kern/86029: undefined reference to `_thread_dump_info' Date: Thu, 22 Sep 2005 08:16:26 -0400 On Sep 21, 2005, at 3:07 PM, Daniel Eischen wrote: > 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. Good to know, sounds like that may be a better solution for this particular situation and esoteric enough to not warrant maintaining the _thread_dump_info() call in order to support older BSD systems that perhaps predate or don't support the SIGINFO behavior. For what it's worth, this bit of code has in fact been used to debug the threading libraries in the past. > I'm going to close this one. You'll need something that > easily regenerates your problem if you file another bug > report on it. Thanks for your suggestions and insight. Cheers! Sean