From owner-freebsd-current Tue Aug 25 01:58:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25262 for freebsd-current-outgoing; Tue, 25 Aug 1998 01:58:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25249 for ; Tue, 25 Aug 1998 01:58:40 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id QAA11737 for ; Tue, 25 Aug 1998 16:56:40 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id PAA29567; Tue, 25 Aug 1998 15:53:48 +0800 Message-Id: <199808250753.PAA29567@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Floating Point Exceptions, signal handlers & subsequent ops Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 15:53:48 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've noticed in one of my applications that the first FP operation after return from a caught SIGFPE is invalid. I have a signal handler installed that just prints out some basic info (like "SIGFPE caught"). The first FP op after this (in my case, converting a long to a double) just gives garbage. Repeat the same statement and it gives a sensible result. Has anyone else seen this before I file a PR with code to reproduce the problem? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message