From owner-freebsd-current@FreeBSD.ORG Sat Apr 8 05:42:53 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from localhost.my.domain (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D05A216A405; Sat, 8 Apr 2006 05:42:52 +0000 (UTC) (envelope-from davidxu@freebsd.org) From: David Xu To: freebsd-current@freebsd.org Date: Sat, 8 Apr 2006 13:42:36 +0800 User-Agent: KMail/1.8.2 References: <20060407140809.GZ1323@beastie.creo.hu> In-Reply-To: <20060407140809.GZ1323@beastie.creo.hu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604081342.36295.davidxu@freebsd.org> Cc: Csaba Henk , Daniel Eischen Subject: Re: switching threading libraries X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 05:42:53 -0000 On Friday 07 April 2006 22:08, Csaba Henk wrote: > On Fri, Apr 07, 2006 at 09:10:56AM -0400, Daniel Eischen wrote: > > Only between libthr and libpthread. libc_r doesn't have symbol > > versioning. > > That's sad -- given, as noted elsewhere, libc_r is the best suitable > for tracing. > > Will it remain like this or can we expect a symver'd libc_r > in due time? > > Regards, > Csaba libc_r does not have debugger can be used, libthr and libpthread do have. libthr can use ktrace to print thread ID, libthr can use top to observe a thread blocked on what event, I don't believe libc_r is best tracable. David Xu