From owner-freebsd-current  Mon May 14 13: 5: 8 2001
Delivered-To: freebsd-current@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0666637B424; Mon, 14 May 2001 13:05:05 -0700 (PDT)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA29504;
	Mon, 14 May 2001 16:05:02 -0400 (EDT)
	(envelope-from wollman)
Date: Mon, 14 May 2001 16:05:02 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200105142005.QAA29504@khavrinen.lcs.mit.edu>
To: Robert Watson <rwatson@FreeBSD.ORG>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: pgm to kill 4.3 via vm
In-Reply-To: <Pine.NEB.3.96L.1010510123858.4086A-100000@fledge.watson.org>
References: <200105092117.RAA74500@khavrinen.lcs.mit.edu>
	<Pine.NEB.3.96L.1010510123858.4086A-100000@fledge.watson.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<<On Thu, 10 May 2001 12:40:42 -0400 (EDT), Robert Watson <rwatson@FreeBSD.ORG> said:

> The process and signal-related structures may be inconsistent if the
> debugger disregards existing locks held over those structures.  It does
> not matter if code is currently still executing, it matters that
> preemption can occur.  The choices appear to be:

Preemption should never occur while the debugger is running.  If those
structures are in an inconsistent state, it *should* be visible to the
debugger.

-GAWollman


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message