Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!bionet!ames!sgi!shinobu!odin!sam!pj
From: pj@sam.sgi.com (Paul Jackson)
Newsgroups: comp.sys.sgi
Subject: Re: preventing core dumps
Message-ID: <4781@odin.SGI.COM>
Date: 1 Mar 90 22:21:24 GMT
References: <221*doelz@urz.unibas.ch>
Sender: news@odin.SGI.COM
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 16

In article <221*doelz@urz.unibas.ch> doelz@urz.unibas.ch (Reinhard Doelz) writes:
| Talking about cores. NOCORE is okay, 
| 
| ... or even a parameter MAXCOREDUMPSIZE, because sometimes a small 
| core is better than nothing, and testing routines it is annoying that 
| your disk gets filled  up with a core which might bother other processes. 

Coming soon to a theater near you.  The next IRIX major
software release includes support for Berkeley style get
and set rlimits, including "limit coredumpsize".  By
setting this limit large enough to include a process's
stack, dbx will provide you a stack backtrace without you
having to dump a Multi-Megabyte core of your data segment.

				Thanks, take care ...
				Paul Jackson (pj@asd.sgi.com), x1373