Path: utzoo!attcan!uunet!cs.utexas.edu!oakhill!nddsun1!digital!digital.sps.mot.com
From: chen@digital.sps.mot.com (Jinfu Chen)
Newsgroups: comp.sys.apollo
Subject: Re: What, no core dump!?
Message-ID: <4e8455b1.1fe60@digital.sps.mot.com>
Date: 10 Dec 90 18:33:02 GMT
References: <1990Dec8.060517.11185@intek01.uucp> <4e790cf9.12c9a@digital.sps.mot.com> <HANCHE.90Dec9171511@hufsa.imf.unit.no>
Sender: news@digital.sps.mot.com
Organization: Motorola, LICD, SPS, Mesa, AZ
Lines: 11
Nntp-Posting-Host: zebra

In article <HANCHE.90Dec9171511@hufsa.imf.unit.no> hanche@imf.unit.no (Harald Hanche-Olsen) writes:
>  (I have not
>been able to figure out under what circumstances I get a traceback and
>when not).

Sometimes tb may tell you no traceback for *current* process. You could
try to use tb -l or tb -all. Also you could force the program to log
information into `node_data/system_logs/proc_dump, see abort(3).

I haven't seen any occasion that tb doesn't log information when a program
crashes. However, I don't write programs for living :-)