David A. Cobb writes:
On 10/09/2008 05:58 AM, Stephen J. Turnbull wrote:
> David A. Cobb writes:
> > And, BTW, there must be an easier way to capture this type
> > of information, isn't there?
>
> No. By the time you get to a crash, XEmacs is dead, and you're
> stuck with system-specific methods. What did you have in mind?
>
How about capturing the message buffer, which I'm assuming would
contain the lisp backtrace, into a file?
No, the Lisp stack trace is grabbed directly from the interpreter
stack, since few crashes occur after Lisp errors, at least we hope so.
In any case, opening files from crashing programs is somewhat
problematic. It is quite common for the program to crash again while
trying to shut down more or less sanely from an unrecoverable error.
This is just not a very useful thing to pursue in my opinion,
certainly not for me (I don't have the skills needed to think about
the internal state of a crashing program).
Or, of course, simply writing the backtrace to a file.
xemacs 2> file-of-your-choice
Alternatively, use the 'lbt' command defined in src/.gdbinit from gdb,
and capture it in the same way as the C stack trace.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta