kern/86029: undefined reference to `_thread_dump_info'

Christopher Sean Morrison brlcad at
Wed Sep 21 11:50:08 PDT 2005

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

From: Christopher Sean Morrison <brlcad at>
To: Daniel Eischen <deischen at>
Cc: David Xu <davidxu at>, bug-followup at
Subject: Re: kern/86029: undefined reference to `_thread_dump_info'
Date: Wed, 21 Sep 2005 14:42:12 -0400

 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.
 >> I've got no issue removing the call from our code, but it seems
 >> indicative of a larger change to what -pthread means.  If -pthread no
 >> longer implies linking against c_r for whatever reason, that would be
 >> the fundamental difference here that we'll need to accommodate in our
 >> build.  In that regard, what non-private routine will provide similar
 >> details when thread creation fails?
 > -pthread means do whatever is necessary to link in the threads
 > library.  In 5.x and subsequent, the threads library is libpthread,
 > not libc_r.
 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?  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.

More information about the freebsd-threads mailing list