summaryrefslogtreecommitdiff
path: root/lispref/debugging.texi
diff options
context:
space:
mode:
authorLute Kamstra <lute@gnu.org>2005-03-04 14:53:15 +0000
committerLute Kamstra <lute@gnu.org>2005-03-04 14:53:15 +0000
commit51827f49030e5a2e30de304c23cab1be9c315f7c (patch)
treea34982e9e2c5b4a41ef35725e5c096b755c68fff /lispref/debugging.texi
parent15cf150db787216573e8be45195fa87c40dae3ec (diff)
(Error Debugging): Document stack-trace-on-error.
Diffstat (limited to 'lispref/debugging.texi')
-rw-r--r--lispref/debugging.texi14
1 files changed, 14 insertions, 0 deletions
diff --git a/lispref/debugging.texi b/lispref/debugging.texi
index 07dfe18f28..5886138eb5 100644
--- a/lispref/debugging.texi
+++ b/lispref/debugging.texi
@@ -166,6 +166,20 @@ this:
(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 non-@code{nil}.
+
+@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