From owner-freebsd-hackers@FreeBSD.ORG  Mon Dec 22 05:36:23 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2FD5416A4CE
	for <hackers@freebsd.org>; Mon, 22 Dec 2003 05:36:23 -0800 (PST)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B955F43D4C
	for <hackers@freebsd.org>; Mon, 22 Dec 2003 05:36:21 -0800 (PST)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id hBMDaFiw027048;
	Mon, 22 Dec 2003 08:36:15 -0500 (EST)
Date: Mon, 22 Dec 2003 08:36:15 -0500 (EST)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Dan Nelson <dnelson@allantgroup.com>
In-Reply-To: <20031222060137.GA87552@dan.emsphone.com>
Message-ID: <Pine.GSO.4.10.10312220835380.26844-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: hackers@freebsd.org
cc: Alfred Perlstein <bright@mu.org>
Subject: Re: support for __thread
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2003 13:36:23 -0000

On Mon, 22 Dec 2003, Dan Nelson wrote:

> In the last episode (Dec 22), Daniel Eischen said:
> > I'd like to stay away from maintaining libc_r any further; not that
> > it can't be done, but with libkse and libthr around, why?
> 
> Do gdb and pstack (in ports) handle libkse or libthr threads?  libc_r

I don't know what pstack is, but we should have gdb for 5.3R.

> is a great debugging tool, if nothing else.  I can't even attach to a
> libkse-threaded program with gdb; the tracee gets SIGSTOP'ped, and gdb
> just sits there.  You have to kill -9 gdb from another tty, and the
> tracee dies.  gdb can attach to a libc_r program, view all the threads,
> and detach without affecting the tracee.