diff options
| author | Lars Ingebrigtsen <larsi@gnus.org> | 2012-09-04 23:21:00 +0200 |
|---|---|---|
| committer | Lars Ingebrigtsen <larsi@gnus.org> | 2012-09-04 23:21:00 +0200 |
| commit | 7f7e0167cf664f2d66ac3fa8a7301e05f09883d2 (patch) | |
| tree | ef9d2dade54e23c6c37e6bd655aae118cdbde261 /doc/lispref/debugging.texi | |
| parent | cf29dd84d205e1c78fed5d1ea0006a382658598c (diff) | |
| download | emacs-7f7e0167cf664f2d66ac3fa8a7301e05f09883d2.tar.gz | |
Implement `debug-on-message'.
This allows tracking down what piece of code is outputting stuff in
the echo area.
* eval.c (call_debugger): Make the function non-static so that we
can call it from set_message.
* xdisp.c (set_message): Implement the new variable `debug-on-message'.
(syms_of_xdisp): Defvar it and `inhibit-debug-on-message'.
Diffstat (limited to 'doc/lispref/debugging.texi')
| -rw-r--r-- | doc/lispref/debugging.texi | 5 |
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 program!) The most common suitable places are inside a @code{progn} or an implicit @code{progn} (@pxref{Sequencing}). + If you don't know exactly where in the source code you want to put +the debug statement, but you want to display a backtrace when a +certain message is displayed, you can set @code{debug-on-message} to a +regular expression matching the desired message. + @node Using Debugger @subsection Using the Debugger |