[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: stack-trace-on-error vs. debug-on-error.
From: |
Lute Kamstra |
Subject: |
Re: stack-trace-on-error vs. debug-on-error. |
Date: |
Fri, 04 Mar 2005 12:09:29 +0100 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
Lute Kamstra <address@hidden> writes:
> I'll document it in the Lisp manual.
Here it is:
*** lispref/debugging.texi 3 Mar 2005 16:28:32 -0000 1.27
--- lispref/debugging.texi 4 Mar 2005 11:02:19 -0000
***************
*** 166,171 ****
--- 166,185 ----
(lambda () (setq debug-on-error t)))
@end example
+ When the debugger is entered, it shows a backtrace (@pxref{Using
+ Debugger}). If you like to see the backtrace when an error happens,
+ but you do not want to enter the debugger, you can set the variable
+ @code{stack-trace-on-error} to address@hidden
+
+ @defopt stack-trace-on-error
+ This variable determines whether a backtrace buffer is shown when an
+ error is signalled and not handled. If @code{stack-trace-on-error} is
+ @code{t}, all kinds of errors display a backtrace; if it is
+ @code{nil}, none do. If the value is a list, an error only means to
+ display a backtrace if one of its condition symbols appears in the
+ list.
+ @end defopt
+
@node Infinite Loops
@subsection Debugging Infinite Loops
@cindex infinite loops