From 51827f49030e5a2e30de304c23cab1be9c315f7c Mon Sep 17 00:00:00 2001 From: Lute Kamstra Date: Fri, 4 Mar 2005 14:53:15 +0000 Subject: [PATCH] (Error Debugging): Document stack-trace-on-error. --- lispref/debugging.texi | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/lispref/debugging.texi b/lispref/debugging.texi index 07dfe18f283..5886138eb55 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 -- 2.39.5