From owner-freebsd-arch  Fri Jan 11 13:27: 6 2002
Delivered-To: freebsd-arch@freebsd.org
Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66])
	by hub.freebsd.org (Postfix) with ESMTP id 9A11137B419
	for <arch@FreeBSD.ORG>; Fri, 11 Jan 2002 13:27:02 -0800 (PST)
Received: from caddis.yogotech.com (caddis.yogotech.com [206.127.123.130])
	by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id OAA01391;
	Fri, 11 Jan 2002 14:22:33 -0700 (MST)
	(envelope-from nate@yogotech.com)
Received: (from nate@localhost)
	by caddis.yogotech.com (8.11.6/8.11.6) id g0BLMXn12951;
	Fri, 11 Jan 2002 14:22:33 -0700 (MST)
	(envelope-from nate)
From: Nate Williams <nate@yogotech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15423.22424.600588.40210@caddis.yogotech.com>
Date: Fri, 11 Jan 2002 14:22:32 -0700
To: Daniel Eischen <eischen@pcnet1.pcnet.com>
Cc: Terry Lambert <tlambert2@mindspring.com>,
	Nate Williams <nate@yogotech.com>, Bruce Evans <bde@zeta.org.au>,
	Dan Eischen <eischen@vigrid.com>, Peter Wemm <peter@wemm.org>,
	Archie Cobbs <archie@dellroad.org>, Alfred Perlstein <bright@mu.org>,
	arch@FreeBSD.ORG
Subject: Re: Request for review: getcontext, setcontext, etc
In-Reply-To: <Pine.SUN.3.91.1020111160903.19846A-100000@pcnet1.pcnet.com>
References: <3C3F500E.A1736EC0@mindspring.com>
	<Pine.SUN.3.91.1020111160903.19846A-100000@pcnet1.pcnet.com>
X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid
Reply-To: nate@yogotech.com (Nate Williams)
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-arch.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-arch>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-arch>
X-Loop: FreeBSD.ORG

> Just to clarify about how POSIX defines signals being delivered to
> threads though...
> 
>   SIGILL, SIGBUS, SIGFPE, etc, are synchronous signals and should
>   be delivered to the current thread (as long as they are unmasked).
> 
> I admit to being somewhat confused by what Bruce wrote also, but
> if we can comply with the above, that would be a good thing.

This is exactly what I'm trying to get clarified.

How can we accomplish it so that these signals/exceptions are properly
reported within the correct context. :) :)


Nate

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