Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!vaxine!wjh12!genrad!grkermit!masscomp!clyde!floyd!harpo!seismo!hao!hplabs!sri-unix!SHAWN@mit-ml
From: SHAWN%mit-ml@sri-unix.UUCP
Newsgroups: net.unix-wizards
Subject: Re:  core dumps
Message-ID: <13186@sri-arpa.UUCP>
Date: Mon, 31-Oct-83 21:41:00 EST
Article-I.D.: sri-arpa.13186
Posted: Mon Oct 31 21:41:00 1983
Date-Received: Fri, 4-Nov-83 07:06:43 EST
Lines: 33

From:  Shawn F. McKay <SHAWN@mit-ml>


Why? if you don't reset the catch, it will core dump the second time,
if you use abort() however, I see your point, but then, you just get
rid of the abort() system call when debug is defined. If you reset
the catch, and have a loop counter, then there is no chance of a loop,
and even without a counter, I don't really see where looping comes in.
Something like this:

#include <stdio.h>
#include <signal.h>

int	trap();

main()
{
	signal(SIGQUIT, trap);		/* bye bye sigquit */
	
	.... body of program

}

trap()
{
	signal(SIGQUIT, trap);		/* reset for next time */
	puts("Ouch!");			/* speak to me! */
}

should NOT loop(??).. if it does, please explain how...

			Yours In Hacking,
			    -Shawn