From owner-freebsd-threads@FreeBSD.ORG  Sun May  9 06:52:56 2004
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5EB5916A4CE; Sun,  9 May 2004 06:52:56 -0700 (PDT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id EE8D643D1D; Sun,  9 May 2004 06:52:55 -0700 (PDT)
	(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 i49DqtpW014467;
	Sun, 9 May 2004 09:52:55 -0400 (EDT)
Date: Sun, 9 May 2004 09:52:55 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Tim Robbins <tjr@freebsd.org>
In-Reply-To: <20040509034044.GA24124@cat.robbins.dropbear.id.au>
Message-ID: <Pine.GSO.4.10.10405090947500.9001-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: threads@freebsd.org
Subject: Re: KSE debugging support - status?
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
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: Sun, 09 May 2004 13:52:56 -0000

On Sun, 9 May 2004, Tim Robbins wrote:

> What is the current status of KSE debugging/GDB support? What's holding it
> up, and when is it likely to be committed?

I believe it's waiting for a GDB import and some kernel thread
id changes.  Marcel is working in perforce on GDB, julian in
perforce on some KSE/thread/scheduling (kernel) restructuring,
and dfr in perforce on TLS support.

-- 
Dan Eischen