From owner-freebsd-current  Fri Oct  3 12:13:04 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA06503
          for current-outgoing; Fri, 3 Oct 1997 12:13:04 -0700 (PDT)
Received: from celebris.tddhome (sil-wa4-51.ix.netcom.com [207.93.136.115])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA06486
          for <freebsd-current@FreeBSD.ORG>; Fri, 3 Oct 1997 12:12:57 -0700 (PDT)
Received: (from tomdean@localhost)
	by celebris.tddhome (8.8.7/8.8.5) id MAA00994;
	Fri, 3 Oct 1997 12:12:50 -0700 (PDT)
Date: Fri, 3 Oct 1997 12:12:50 -0700 (PDT)
Message-Id: <199710031912.MAA00994@celebris.tddhome>
From: Thomas Dean <tomdean@ix.netcom.com>
To: freebsd-current@FreeBSD.ORG
Subject: Re: xlock: caught signal 8 while running galaxy mode.
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

FreeBSD clears the exception register in the fpu when the trap code
catches an fpu exception prior to calling the user's handler, if any.

In npx.c, the exception register is cleared prior to sending a SIGFPE
to the process.

I want to be able to catch an exception, if I want, and determine what
the cause of the problem was, and, possibly work around it.  I want my
exception handler to know exactly what the exception was.

tomdean