Path: utzoo!attcan!uunet!sco!seanf
From: seanf@sco.COM (Sean Fagan)
Newsgroups: comp.unix.internals
Subject: Re: Checking Exit Codes (was: Re: Trojan Horses)
Message-ID: <8508@scolex.sco.COM>
Date: 31 Oct 90 07:25:23 GMT
References: <18647@rpp386.cactus.org> <4057@awdprime.UUCP> <18658@rpp386.cactus.org>
Sender: news@sco.COM
Reply-To: seanf (Sean Fagan)
Organization: The Santa Cruz Operation, Inc.
Lines: 20


In article <18658@rpp386.cactus.org> jfh@rpp386.cactus.org (John F. Haugh II) writes:
>so, you will always assume that failing asserts never return?  

Yes.  I believe that's what ANSI (and POSIX) says.  At least one
implementation (ours, to be honest 8-)) makes sure that abort() will not
return.  The only way, from my glancing of the object code (disassembled, of
course), to get it to return would be to send the process a signal it *does*
catch, and then longjmp() out of that signal handler.

But there's now way I know of to make sure that such a thing doesn't happen.
(Well, you could, in abort(), block all signals, I suppose, and, now that I
think about it, I think I'll see about getting us to do so 8-).)

-- 
-----------------+
Sean Eric Fagan  | "Quoth the raven,"
seanf@sco.COM    | "Eat my shorts!"
uunet!sco!seanf  |     -- Lisa and Bart Simpson
(408) 458-1422   | Any opinions expressed are my own, not my employers'.