Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!rutgers!sri-spam!mordor!lll-crg!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix
Subject: Re: catching FPEs?
Message-ID: <3678@umcp-cs.UUCP>
Date: Fri, 3-Oct-86 17:05:23 EDT
Article-I.D.: umcp-cs.3678
Posted: Fri Oct  3 17:05:23 1986
Date-Received: Sat, 4-Oct-86 13:07:40 EDT
References: <371@vu-vlsi.UUCP>
Organization: Computer Sci. Dept, U of Maryland, College Park, MD
Lines: 15

In article <371@vu-vlsi.UUCP> colin@vu-vlsi.UUCP (Colin Kelley) writes:
>... Is there some way to trap FPEs and then indicate that you want
>to resume execution _after_ the code which caused the FPE?

Yes, but this is extermely machine dependent.

If you peer closely at the 4.2 or 4.3 BSD signal manual entries,
you will find something called `sigcontext'.  This includes enough
of the call frame so that you can alter the return point, and the
stack pointer and/or frame pointers if necessary.  The way to do
this is no doubt quite different on a Pyramid than on a Vax.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1516)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu