Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!ee.udel.edu From: new@ee.udel.edu (Darren New) Newsgroups: comp.sys.next Subject: Re: Core dump sanity Message-ID: <49911@nigel.ee.udel.edu> Date: 5 Apr 91 19:13:43 GMT References: Sender: usenet@ee.udel.edu Organization: University of Delaware Lines: 18 Nntp-Posting-Host: snow-white.ee.udel.edu In article scott@texnext.gac.edu (Scott Hess) writes: >So, what I would like is for people to insert the following code, >or something much like it, into their distributed programs. This >will cause you program _not_ to dump core if there are problems. >Since few (if any) of the users will have the source to debug >with anyhow, it's not a loss: Bad idea. Then when a user has problems with your program which you cannot duplicate, it is impossible for the user to send you a copy of the core file for you to inspect against your proprietary sources. Much better to just fix the problem properly using the inheritence of user limits as it was meant to be used. -- Darren -- --- Darren New --- Grad Student --- CIS --- Univ. of Delaware --- ----- Network Protocols, Graphics, Programming Languages, FDTs ----- +=+=+ My time is very valuable, but unfortunately only to me +=+=+ + When you drive screws with a hammer, screwdrivers are unrecognisable +