[comp.sys.apollo] tracebacks

kurt@MOHO.MIT.EDU (Kurt Feigl) (06/28/89)

  I am poor graduate student trying to debug ugly fortran code inherited
from the stone ages.  
  After an error, I would like to be able to do a traceback 
before exiting the program.  At the moment, I can't come up with a
better way than exiting through a SUICID routine which displays an error
message and divides by zero.  Unless I do this ugly kluge, the STOP seems
to clean up the stack enough to render the traceback (tb) meaningless.

  There must be a better way, perhaps a system call?

  Thanks.
  Kurt Feigl
  
  kurt@benioff.mit.edu

FERGUSON@TMASL.EXXON.COM (06/29/89)

The system call (Aegis, that is) pfm_$error_trap will save a traceback
for you, and I think it will also exit the program, with one of those
fault messages. The limitation is that you have to have the status code
to pass to it.

in Fortran,

      call pfm_$error_trap(status)

Good luck,
Scott Ferguson
Exxon Research & Engineering