Commit 66249842 authored by Lars Magne Ingebrigtsen's avatar Lars Magne Ingebrigtsen
Browse files

(Using Debugger): Mention @code{eval-expression-debug-on-error}

Fixes: debbugs:8549
parent 1d698799
2011-07-15 Lars Magne Ingebrigtsen <>
* debugging.texi (Using Debugger): Mention
@code{eval-expression-debug-on-error} (bug#8549).
2011-07-14 Eli Zaretskii <>
* display.texi (Other Display Specs): Document that `left-fringe'
......@@ -306,6 +306,16 @@ and it is wise to go back to the backtrace buffer and exit the debugger
the debugger gets out of the recursive edit and kills the backtrace
When the debugger has been entered, the @code{debug-on-error}
variable is temporarily set according to
@code{eval-expression-debug-on-error}. If the latter variable is
non-@code{nil}, @code{debug-on-error} will temporarily be set to
@code{t}. This means that any further errors that occur while doing a
debugging session will (by default) trigger another backtrace. If
this is not want you want, you can either set
@code{eval-expression-debug-on-error} to @code{nil}, or set
@code{debug-on-error} to @code{nil} in @code{debugger-mode-hook}.
@cindex current stack frame
The backtrace buffer shows you the functions that are executing and
their argument values. It also allows you to specify a stack frame by
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment