Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!bu-cs!bloom-beacon!mit-eddie!apollo!oj
From: oj@apollo.COM (Ellis Oliver Jones)
Newsgroups: comp.sys.apollo
Subject: Re:  SR10 /com/tb
Message-ID: <42fbc010.d5b2@apollo.COM>
Date: 2 May 89 16:16:00 GMT
References: <8904291529.AA00418@lnic1.hprc.uh.edu> <42f7bbce.1b147@apollo.COM>
Reply-To: oj@canyon.UUCP (Ellis Oliver Jones)
Organization: Apollo Computer, Chelmsford, MA
Lines: 10

In article <42f7bbce.1b147@apollo.COM> nazgul@apollo.COM (Kee Hinckley) writes:
>That's just weird.  Unless the program really blew itself
>away, a 'tb -l' (show last program traceback) works fine
>for me.

Some application programs have fault handlers which ``recover'' 
from faults by fixing them up, then printing a message and 
exiting.  This is irritating, as it prevents tracebacks.  
Could this be the problem?
/oj