Date: Fri, 11 Jan 2002 14:22:32 -0700 From: Nate Williams <nate@yogotech.com> 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 Message-ID: <15423.22424.600588.40210@caddis.yogotech.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15423.22424.600588.40210>