Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!spool.mu.edu!uunet!mcsun!sun4nl!eur.nl!pk From: pk@cs.few.eur.nl (Paul Kranenburg) Subject: Re: Program dies with FP Exception Message-ID: <1992Sep14.151555.12300@cs.few.eur.nl> Sender: news@cs.few.eur.nl Reply-To: pk@cs.eur.nl Organization: Erasmus University Rotterdam References: <STARK.92Sep13002650@sbstark.cs.sunysb.edu> <1992Sep13.083846.6134@fcom.cc.utah.edu> Date: Mon, 14 Sep 1992 15:15:55 GMT Lines: 16 In <1992Sep13.083846.6134@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes: >In article <STARK.92Sep13002650@sbstark.cs.sunysb.edu> stark@cs.sunysb.edu (Gene Stark) writes: >>Here's a tough one I've been trying to track down -- maybe somebody out there >>who knows more can guess what is going on. >> [...] >First of all, like all other signals, the SIGFPE gets delivered to a process >as a result of the sigtrampoline code. The *only* way you get a signal is >on return from a system call. The problem is that there appears to be no ... or you get your signal immediately, provided you have a handler set, or you get it on return from the interrupt (trap), provided the AST (Async. System Trap) stuff is implemented which is then invoked from `signotify()'. -pk