Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 beta 3/9/83; site cwruecmp.UUCP
Path: utzoo!linus!decvax!cwruecmp!glassner
From: glassner@cwruecmp.UUCP (Andrew Glassner)
Newsgroups: net.unix-wizards
Subject: Disabling core dumps
Message-ID: <735@cwruecmp.UUCP>
Date: Sat, 22-Oct-83 13:54:00 EDT
Article-I.D.: cwruecmp.735
Posted: Sat Oct 22 13:54:00 1983
Date-Received: Sun, 23-Oct-83 08:25:14 EDT
Organization: CWRU Computer Engr. Cleveland, Ohio
Lines: 25

I currently have a C program which has got some bugs.     
One set of bugs causes the program to dump core; it runs
into a segmentation error and it's all over.
I know that the cause of this problem is in the logic of
some code that generates a data structure; there's nothing
to learn from the core dump.
The problem is that sometimes the core dump IS useful for
fixing other errors; I compile with -g so that I can use 
sdb to examine variables, etc.
Often though I don't want the core dump.  Unfortunately, the
C program is big and the core dump takes upwards of a minute
or more, which I must spend sitting and waiting for my
terminal to come back.

Question:  Is there some way to suppress a core dump, so that
           when the program bombs I just get the error message
           and my terminal comes back?  

Supporting info:  We're running 4.1BSD on a VAX-11/780.

	Thanks!

	-Andrew		Andrew  Glassner    decvax!cwruecmp!glassner