Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!hsdndev!spdcc!tauxersvilli!alphalpha!nazgul From: nazgul@alphalpha.com (Kee Hinckley) Newsgroups: comp.sys.apollo Subject: Re: What, no core dump!? Message-ID: <1990Dec11.182545.10709@alphalpha.com> Date: 11 Dec 90 18:25:45 GMT References: <1990Dec8.060517.11185@intek01.uucp> <4e790cf9.12c9a@digital.sps.mot.com> <4e8455b1.1fe60@digital.sps.mot.com> Organization: asi Lines: 20 In article <4e8455b1.1fe60@digital.sps.mot.com> chen@digital.sps.mot.com (Jinfu Chen) writes: >I haven't seen any occasion that tb doesn't log information when a program >crashes. However, I don't write programs for living :-) Under certain circumstances this may happen, but it isn't too common. Stack corruption or a full disk might not get logged (well, full disk *certainly* wouldn't get logged :-). Also the traceback doesn't actually store the symbol information, it looks that up in the object. So if you delete the program object the traceback is no longer useful. All in all though I prefer tb to core dumps most of the time, the other 10% are a pain though. -- Alphalpha Software, Inc. | motif-request@alphalpha.com nazgul@alphalpha.com |----------------------------------- 617/646-7703 (voice/fax) | Proline BBS: 617/641-3722 I'm not sure which upsets me more; that people are so unwilling to accept responsibility for their own actions, or that they are so eager to regulate everyone else's.