aboutsummaryrefslogtreecommitdiffstats
path: root/doc/lispref/debugging.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/lispref/debugging.texi')
-rw-r--r--doc/lispref/debugging.texi5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index 00e8d84e9b3..5aeff576d09 100644
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -298,6 +298,11 @@ of @code{(debug)} isn't ignored, it will alter the execution of the
298program!) The most common suitable places are inside a @code{progn} or 298program!) The most common suitable places are inside a @code{progn} or
299an implicit @code{progn} (@pxref{Sequencing}). 299an implicit @code{progn} (@pxref{Sequencing}).
300 300
301 If you don't know exactly where in the source code you want to put
302the debug statement, but you want to display a backtrace when a
303certain message is displayed, you can set @code{debug-on-message} to a
304regular expression matching the desired message.
305
301@node Using Debugger 306@node Using Debugger
302@subsection Using the Debugger 307@subsection Using the Debugger
303 308