Xref: utzoo comp.lang.misc:5456 comp.unix.internals:82
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!uupsi!ccavax!merriman
From: merriman@ccavax.camb.com
Newsgroups: comp.lang.misc,comp.unix.internals
Subject: Re: Unix error handling
Message-ID: <31815.26e5731a@ccavax.camb.com>
Date: 6 Sep 90 01:50:18 GMT
References: <861@dg.dg.com> <12023:Aug3017:24:1590@kramden.acf.nyu.edu> <1990Aug31.190751.12522@dg-rtp.dg.com> <556:Aug3122:09:3290@kramden.acf.nyu.edu> <1990Sep2.050854.12008@nixtdc.uucp>
Distribution: usa
Organization: Cambridge Computer Associates, Inc.
Lines: 17

In article <1990Sep2.050854.12008@nixtdc.uucp>, 
	doug@nixtdc.uucp (Doug Moen) writes:

[stuff deleted]

> Here's the obligatory new idea:
> I don't like the fact that Unix kills a process if it blows the stack
> due to an infinite recursive loop.  The problem could be fixed with
> the introduction of an exception handling mechanism that the kernel
> knows about.  If the stack overflows, then the kernel raises an exception
> within the offending process.  The exception unwinds the stack (thereby
> recovering stack space) until a stack frame containing an exception
> handler is found.  If no exception handler is active, then (and only then)
> is the process killed.
> -- 

Sounds a lot like VMS exception handlers