Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!harpo!seismo!hao!hplabs!sri-unix!ron@brl-vgr
From: ron%brl-vgr@sri-unix.UUCP
Newsgroups: net.unix-wizards
Subject: Re:  core dumps
Message-ID: <13187@sri-arpa.UUCP>
Date: Mon, 7-Nov-83 00:54:34 EST
Article-I.D.: sri-arpa.13187
Posted: Mon Nov  7 00:54:34 1983
Date-Received: Fri, 4-Nov-83 06:27:32 EST
Lines: 21

From:      Ron Natalie <ron@brl-vgr>

But that's not what you said.  You said SIG_IGN.  That's ignore.
That means the program never has any indication that it trapped.
This will either cause the program to continue errouneously or
cause it to enter a rather strange loop.

I feel that it is more versatile to disable core dumps external
to the program because it allows the shell to still give you the
notification of the exception and allows you to easily turn them
back on again if you want them.  The two ways of disabling core
dumps, but keeping the standard exception processing demonstrated
for 4.1 BSD so far are chaning the limit on the core dump size to
zero or just making the file "core" such that it is non writable.

Even if one was to use your method of ignoring exceptions, wouldn't
it be easier to write a program similar to the "nohup" utility that
sets all the signals to IGNORE and then execs the program, this would
preclude having to modify the program to turn them on and off.

-Ron