From owner-freebsd-arch Wed Jan 9 19:17:26 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 333F737B41C for ; Wed, 9 Jan 2002 19:17:22 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id OAA02147; Thu, 10 Jan 2002 14:16:56 +1100 Date: Thu, 10 Jan 2002 14:17:43 +1100 (EST) From: Bruce Evans X-X-Sender: To: Nate Williams Cc: Daniel Eischen , Dan Eischen , Peter Wemm , Archie Cobbs , Alfred Perlstein , Subject: Re: Request for review: getcontext, setcontext, etc In-Reply-To: <15420.58839.954146.527043@caddis.yogotech.com> Message-ID: <20020110141330.M10745-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > Assuming I used followed things up with 'fnsave', will the exception be > > > triggered by a frstor, and thus the exception will be correctly reported > > > by the thread triggering the exception? > > > > Only on broken systems. > > Why is reporting a SIGFPE considered broken? This is a valid exception, > and it should be reported. Because the SIGFPE is for the broken context-switching code and not for the program. > > See Appendix C of the Intel MMX manual (1997 version at least) for more > > details. > > I don't have the MXX manual, just the x86/87 programming manuals for x86 > (X <= 3). Same here, except I also have the 486 manual and a web browser :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message