home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!Sirius.dfn.de!Urmel.Informatik.RWTH-Aachen.DE!dfv.rwth-aachen.de!sungate.fido.de!p1.hippo.fido.de!eurologic.fido.de!Martin_Schloeter
- Date: Wed, 2 Sep 92 10:11:14 +0200
- From: Martin_Schloeter@eurologic.fido.de (Martin Schloeter)
- Subject: Re: How to catch floating point exceptions (under Watcom C/386)?
- Message-ID: <199bb4a8@p3.f67.n245.z2.fidonet.org>
- Newsgroups: comp.os.ms-windows.programmer.misc
- X-Comment-To: (Robert Lansdale)
- Organization: Die ersten 100.000 Jahre...
- Lines: 11
-
- RL> After a bit of debugging I came to realization today that the
- RL> normal UNIX-like signal() handling mechanism does not function under
- RL> Windows 3.1. In particular, it does not function when using Watcom C/386
- RL> with their Windows 32-bit supervisor. A quick search through my Windows
- RL> books turned up nothing and none of the FAQs mentioned exception handling.
- RL> So, how may I intercept a signal in Windows, in particular a floating
- RL> point exception?
- With 3.1 comes the TOOLHELP.DLL which supports a kind of exception hooks. Look
- for InterruptRegister in the 3.1 SDK Online-Help.
-
- Martin
-