Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 May 2001 18:38:07 -0400 (EDT)
From:      Robert Watson <rwatson@FreeBSD.ORG>
To:        Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: pgm to kill 4.3 via vm
Message-ID:  <Pine.NEB.3.96L.1010514183649.77894A-100000@fledge.watson.org>
In-Reply-To: <200105142005.QAA29504@khavrinen.lcs.mit.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 14 May 2001, Garrett Wollman wrote:

> <<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. 

Yes, exactly.  The debugger my preempt, and the structures may be in an
inconsistent state.  Therefor, caution must be used when making use of
functions that assume a consistent state, or attempt to make use of locks
which may already be held but cannot be released. 

Robert N M Watson             FreeBSD Core Team, TrustedBSD Project
robert@fledge.watson.org      NAI Labs, Safeport Network Services



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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1010514183649.77894A-100000>