🚀 go-pugleaf

+From:	SMTP%"karish@pangea.stanford.edu" 12-JAN-1993 06:17:29.17
+To:	info-iris-misc@BRL.MIL
+CC:	
+Subj:	Re: developing under sys 5 unix

+From: Chuck Karish <karish@pangea.stanford.edu>
+Newsgroups: comp.sys.sgi,comp.unix.programmer
+Subject: Re: developing under sys 5 unix
+Message-ID: <1993Jan11.214558.11272@leland.Stanford.EDU>
+Date: 11 Jan 93 21:45:58 GMT
+Sender: Mr News <news@leland.stanford.edu>
+To:       info-iris-misc@BRL.MIL

+In article <1993Jan11.202845.12276@lincroftnj.ncr.com>
+rjf@lincroftnj.ncr.com (51351[efw]-Robert Feddeler(MT4799)T343) writes:
+|In article <1993Jan11.190843.6808@CSD-NewsHost.Stanford.EDU>
+vahe@sparcy.Stanford.EDU (Vahe Avedissian) writes:

+Hi, Vahe!

+||The real annoying thing is once you run a program
+||with a bug, the system tends to completely stop responding
+||to interrupts or anything else, the windowing
+||system and manager are rendered unresponsive too.
+||You just sit there and wait for the system to eventually
+||(i.e. anywhere from 3 - 10 minutes or so) core dump.
|
+|I've experienced this a few of times.  The bug always turns out
+|to be an out-of-control recursive function.  The process eventually
+|runs out of swap space or exceeds the limits on process virtual memory
+|as the stack grows.  It takes a while to page all that stack out, and
+|then read it back and write the 'core' file.
|
+|Try a smaller, faster disk...  {8^)

+Or use csh for your shell, and use 'limit stacksize' and
+'limit coredumpsize' to keep the process from being such
+a resource hog.
+--

+    Chuck Karish          karish@mindcraft.com
+    (415) 323-9000 x117   karish@pangea.stanford.edu

Or, use a better shell, ksh:

	ulimit -s 999
	ulimit -c 999

Replace the 999's with your desired limits.  These do the same operations
as the corresponding `csh' statements.

(re `csh': try sending command normal output to a file and error output down
a pipe without a subshell.  This is easy with either Bourne or Korn shell.
Try nested command output quoting.  This is easy with Korn shell. ....)

Randolph J. Herber, herber@fnalf.fnal.gov, +1 708 840 2966
(Speaking for myself and not for US, US DOE, FNAL nor URA.)
(Product, trade, or service marks herein belong to their respective owners.)