Hello,
we want to build a 'fail safe' function for our application, that is:
If an error occurs, we want to catch the error, write an error report
(error message, function hierarchy) into a file and finish the
application in a consistent manner.
The environment: SUN SPARCstation 2, SunOS 4.1.2, Lucid Lisp 4.0
Our problem: How can we locate the origin of the error (function
hierarchy), when we have caught a condition object. Any hints welcome.
+----------------------------------------------------------------------+
| Rainer Weidemann email ········@iai.kfk.de |
| Kernforschungszentrum Karlsruhe GmbH |
| IAI, Abt. Umweltinformatik __ |
| Postfach 3640 |__)| | phone +49 7247 82-5740 |
| W-7500 Karlsruhe 1, Germany | \ |/\| fax +49 7247 82-5786 |
+----------------------------------------------------------------------+
In article <··········@iai.kfk.de> ········@iai.kfk.de writes:
>we want to build a 'fail safe' function for our application, that is:
>If an error occurs, we want to catch the error, write an error report
>(error message, function hierarchy) into a file and finish the
>application in a consistent manner.
>
>The environment: SUN SPARCstation 2, SunOS 4.1.2, Lucid Lisp 4.0
See the section "DEBUGGER INFORMATION" in the wizards.doc file that comes
with Lucid CL. It documents functions for examining the stack. You can
locate the source of the error by searching up the stack for a call to
ERROR or SIGNAL, and dump the function hierarchy by continuing up the stack
further.
Hey, Mark -- I think the FAQ should contain a reference to Lucid's
wizards.doc file. Perhaps even its table of contents.
--
Barry Margolin
System Manager, Thinking Machines Corp.
······@think.com {uunet,harvard}!think!barmar