Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!shaman!jiro From: jiro@shaman.com (Jiro Nakamura) Newsgroups: comp.sys.next Subject: Re: Core dump sanity Message-ID: <1991Apr6.215703.9818@shaman.com> Date: 6 Apr 91 21:57:03 GMT References: <49911@nigel.ee.udel.edu> Organization: Shaman Consulting Lines: 21 In article <49911@nigel.ee.udel.edu> new@ee.udel.edu (Darren New) writes: >> [Setting it so a program won't core dump, ever] >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 A user once sent me a coredump of Cassandra. I was wondering why my Trailblazer seemed hung up on one file for a hell of a long time. :-( Getting multi-megabyte coredumps over a UUCP line isn't one's idea of fun. But I agree, the user should have the option of making his or her own coredump and debugging it with gdb if they really want to. Freedom to the users. :-) - jiro -- Jiro Nakamura jiro@shaman.com Shaman Consulting (607) 253-0687 VOICE "Bring your dead, dying shamans here!" (607) 253-7809 FAX/Modem