From owner-freebsd-current@FreeBSD.ORG  Mon Jun 21 19:07:58 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 746B216A4CE; Mon, 21 Jun 2004 19:07:58 +0000 (GMT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1126143D2D; Mon, 21 Jun 2004 19:07:58 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i5LJ7gRm049126;
	Mon, 21 Jun 2004 12:07:52 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200406211907.i5LJ7gRm049126@gw.catspoiler.org>
Date: Mon, 21 Jun 2004 12:07:42 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: bde@zeta.org.au
In-Reply-To: <20040621220455.T9194@gamplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: threads@FreeBSD.org
cc: rwatson@FreeBSD.org
cc: current@FreeBSD.org
Subject: Re: calcru: negative time ... followed by freeze
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jun 2004 19:07:58 -0000

On 21 Jun, Bruce Evans wrote:
> On Mon, 21 Jun 2004, Don Lewis wrote:

>> It also looks like a bug that a zombie remains in the [running] state
>> and thus looks interesting to ttyinfo().
> 
> I think it isn't really running.  ttyinfo() should pick it if it is the
> only process the terminal.  ttyinfo() does pick it for the zombie in the
> test program in the PR, and reports that it is running, but ps reports
> it correctly as a zomble.

ttyinfo() prints "[running]" if TD_IS_RUNNING(td) is true.  I think the
problem is that thread_exit() doesn't set td_state to TDS_INACTIVE if
the process only has one thread.