home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!destroyer!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!think.com!barmar
- From: barmar@think.com (Barry Margolin)
- Newsgroups: comp.lang.c
- Subject: Re: ANSI description for signal handling
- Date: 1 Sep 1992 16:05:06 GMT
- Organization: Thinking Machines Corporation, Cambridge MA, USA
- Lines: 13
- Message-ID: <1804biINN944@early-bird.think.com>
- References: <9208311517.AB03610@ucbvax.Berkeley.EDU> <1992Sep1.020305.15064@thinkage.on.ca>
- NNTP-Posting-Host: telecaster.think.com
-
- In article <1992Sep1.020305.15064@thinkage.on.ca> atbowler@thinkage.on.ca (Alan Bowler) writes:
- > In the case of an implicit raise,
- >you can only call signal() with the SAME signal number, and you can
- >only get out of the handler by doing a return.
-
- But the quoted passage also says that if you do a return from a handler
- that was called due to SIGFPE, the behavior is undefined. So, if SIGFPE is
- raised implicitly, there's no way to get out of the handler!
- --
- Barry Margolin
- System Manager, Thinking Machines Corp.
-
- barmar@think.com {uunet,harvard}!think!barmar
-