Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ulowell!apollo!nazgul
From: nazgul@apollo.COM (Kee Hinckley)
Newsgroups: comp.sys.apollo
Subject: Re:  SR10 /com/tb
Message-ID: <42f7bbce.1b147@apollo.COM>
Date: 1 May 89 21:06:00 GMT
References: <8904291529.AA00418@lnic1.hprc.uh.edu>
Reply-To: nazgul@apollo.COM (Kee Hinckley)
Organization: Apollo Computer, Chelmsford, MA
Lines: 17

>with the same code compiled under the ftn front-end.  The
>response to my APR came yesterday, and they told me that Unix
>has "no concept" of a traceback (yes we've all gotten those
>core dumps"), so a tb invoked immediately after bombing a
>Unix compiled code would do nothing for me.  Hence you have
>three options as I see it: (1) tb -n //node_spec , (2) set your
>f77_dump_flag environment to "y", or (3) compile with the -g
>switch (or you could use /com/ftn and /com/cc as we do).
>
That's just weird.  Unless the program really blew itself
away, a 'tb -l' (show last program traceback) works fine
for me.
-- 
### User Environment, Apollo Computer Inc. ###  Public Access ProLine BBS   ###
###     {mit-eddie,yale}!apollo!nazgul     ###  nazgul@pro-angmar.cts.com   ###
###           nazgul@apollo.com            ### (617) 641-3722 300/1200/2400 ###
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.