Article View: comp.os.msdos.programmer
Article #4319Trapping Floating Point Errors in Turbo C
From: Steve Resnick
Date: Tue, 22 Jan 1991 21:22
Date: Tue, 22 Jan 1991 21:22
14 lines
1094 bytes
1094 bytes
I have a problem - I need to trap floating point errors from the floating point hardware. Currently, I am using signal() to do this, but signal doesn't give me some of the information I need. I assume that the 80n87 and the emulator (EMU.LIB) both generate an interrupt in the event of a floating point exception. My question is, what interrupt is generated, and if the ISR for that interrupt is shared, what do I need to check on the PIC to determine the source of the interupt? One of the things I want, which I can't get out of signal, is the CS:IP at the time of the exception, so that I can point the finger at a specific routine. Thanx, in advance, Steve
Technical Details
Message-ID:
<21650@netcom.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!cs.utexas.edu!sun-barr!apple!netcom!netcom.UUCPShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!cs.utexas.edu!sun-barr!apple!netcom!netcom.UUCP
From: resnicks@netcom.UUCP (Steve Resnick)
Newsgroups: comp.os.msdos.programmer,alt.msdos.programmer
Subject: Trapping Floating Point Errors in Turbo C
Message-ID: <21650@netcom.UUCP>
Date: 22 Jan 91 21:22:16 GMT
Sender: resnicks@netcom.UUCP
Organization: Netcom- The Bay Area's Public Access Unix System {408 241-9760 guest}
Lines: 14