@cindex backtrace buffer
Debugger mode is derived from Backtrace mode, which is also used to
-show backtraces by Edebug and ERT. (@pxref{Edebug} and @ref{Top,the
-ERT manual,, ert, ERT: Emacs Lisp Regression Testing})
+show backtraces by Edebug and ERT. (@pxref{Edebug}, and @ref{Top,the
+ERT manual,, ert, ERT: Emacs Lisp Regression Testing}.)
@cindex stack frame
The backtrace buffer shows you the functions that are executing and
move to it and type @key{RET}, to visit the source code. You can also
type @key{RET} while point is on any name of a function or variable
which is not underlined, to see help information for that symbol in a
-help buffer, if any exists. The @code{xref-find-definitions} command,
+help buffer, if any exists. The @code{xref-find-definitions} command,
bound to @key{M-.}, can also be used on any identifier in a backtrace
-(@pxref{Looking Up Identifiers,,,emacs,Emacs manual}).
+(@pxref{Looking Up Identifiers,,,emacs, The GNU Emacs Manual}).
In backtraces, the tails of long lists and the ends of long strings,
vectors or structures, as well as objects which are deeply nested,
shows the function followed by a list of the values of the function's
arguments if they are all known; if they are still being computed, the
line consists of a list containing the function and its unevaluated
-arguments. Long lists or deeply nested structures may be elided.
+arguments. Long lists or deeply nested structures may be elided.
@smallexample
@group
Display a backtrace, excluding Edebug's own functions for clarity
(@code{edebug-backtrace}).
-@xref{Debugging,, Backtraces, elisp}, for a description of backtraces
+@xref{Backtraces}, for a description of backtraces
and the commands which work on them.
If you would like to see Edebug's functions in the backtrace,
definition of the test near point (@kbd{@key{RET}} has the same effect
if point is on the name of the test). On a failed test, @kbd{b} shows
the backtrace of the failure. @xref{Debugging,, Backtraces, elisp,
-the Emacs Lisp Reference Manual}, for more information about
+GNU Emacs Lisp Reference Manual}, for more information about
backtraces.
@kindex l@r{, in ert results buffer}
+++
*** The Lisp Debugger is now based on 'backtrace-mode'.
Backtrace mode adds fontification and commands for changing the
-appearance of backtrace frames. See the node "Backtraces" in the Elisp
+appearance of backtrace frames. See the node "Backtraces" in the Elisp
manual for documentation of the new mode and its commands.
** Edebug
globally or for individual definitions.
+++
-*** Edebug's backtrace buffer now uses 'backtrace-mode'. Backtrace
-mode adds fontification, links and commands for changing the
-appearance of backtrace frames. See the node "Backtraces" in the Elisp
+*** Edebug's backtrace buffer now uses 'backtrace-mode'.
+Backtrace mode adds fontification, links and commands for changing the
+appearance of backtrace frames. See the node "Backtraces" in the Elisp
manual for documentation of the new mode and its commands.
The binding of 'd' in Edebug's keymap is now 'edebug-pop-to-backtrace'
+++
*** ERT's backtrace buffer now uses 'backtrace-mode'.
Backtrace mode adds fontification and commands for changing the
-appearance of backtrace frames. See the node "Backtraces" in the Elisp
+appearance of backtrace frames. See the node "Backtraces" in the Elisp
manual for documentation of the new mode and its commands.
** Gamegrid
** Backtrace mode improves viewing of Elisp backtraces.
Backtrace mode adds pretty printing, fontification and ellipsis
expansion to backtrace buffers produced by the Lisp debugger, Edebug
-and ERT. See the node "Backtraces" in the Elisp manual for
+and ERT. See the node "Backtraces" in the Elisp manual for
documentation of the new mode and its commands.
\f