Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!psuvax1!brutus.cs.uiuc.edu!samsung!uunet!crdgw1!crdgw1.ge.com!barnett From: barnett@crdgw1.crd.ge.com (Bruce Barnett) Newsgroups: comp.unix.questions Subject: Re: Some core dump questions Keywords: remember what you have in your .cshrc Message-ID: <5040@crdgw1.crd.ge.com> Date: 1 Feb 90 11:52:03 GMT References: <5458@hydra.gatech.EDU> <1990Jan31.070404.17399@athena.mit.edu> <21995@unix.cis.pitt.edu> Sender: news@crdgw1.crd.ge.com Reply-To: barnett@crdgw1.crd.ge.com (Bruce Barnett) Organization: GE Corp. R & D, Schenectady, NY Lines: 22 In-reply-to: yahoo@unix.cis.pitt.edu (Kenneth L Moore) >> Doing a "limit coredumpsize 0" in the default .cshrc file *is* the >>right way to do it. > In article <21995@unix.cis.pitt.edu>, yahoo@unix (Kenneth L Moore) writes: >Of course when you need a core, for use with dbx for example, you are up >THE creek. Well, most of the time the programmer wants core dumps in a project directory, and not in other directories (unless they like reporting bugs to other people). What you could do is to automatically change your core dump size whenever you change directories to your project directory. Having appropriate entires in the file ./.dir might do it if you redefined your cd command to be: alias cd 'chdir \!*; if ( -f .dir && -o .dir ) source .dir ' -- Bruce G. Barnett uunet!crdgw1!barnett