Mercurial > emacs
changeset 43286:3fda6d6f3078
Explain about underlined functions in debugger buffer.
Minor clarification.
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Thu, 14 Feb 2002 00:38:41 +0000 |
| parents | 11229f89ded6 |
| children | 431e14e1690f |
| files | lispref/debugging.texi |
| diffstat | 1 files changed, 13 insertions(+), 12 deletions(-) [+] |
line wrap: on
line diff
--- a/lispref/debugging.texi Wed Feb 13 22:55:23 2002 +0000 +++ b/lispref/debugging.texi Thu Feb 14 00:38:41 2002 +0000 @@ -316,6 +316,10 @@ considered the @dfn{current frame}. Some of the debugger commands operate on the current frame. + If a function name is underlined, that means the debugger knows +where its source code is located. You can click @kbd{Mouse-2} on that +name, or move to it and type @key{RET}, to visit the source code. + The debugger itself must be run byte-compiled, since it makes assumptions about how many stack frames are used for the debugger itself. These assumptions are false if the debugger is running @@ -327,18 +331,15 @@ @subsection Debugger Commands @cindex debugger command list - Inside the debugger (in Debugger mode), these special commands are -available in addition to the usual cursor motion commands. (Keep in -mind that all the usual facilities of Emacs, such as switching windows -or buffers, are still available.) - - The most important use of debugger commands is for stepping through -code, so that you can see how control flows. The debugger can step -through the control structures of an interpreted function, but cannot do -so in a byte-compiled function. If you would like to step through a -byte-compiled function, replace it with an interpreted definition of the -same function. (To do this, visit the source for the function and type -@kbd{C-M-x} on its definition.) + The debugger buffer (in Debugger mode) provides special commands in +addition to the usual Emacs commands. The most important use of +debugger commands is for stepping through code, so that you can see +how control flows. The debugger can step through the control +structures of an interpreted function, but cannot do so in a +byte-compiled function. If you would like to step through a +byte-compiled function, replace it with an interpreted definition of +the same function. (To do this, visit the source for the function and +type @kbd{C-M-x} on its definition.) Here is a list of Debugger mode commands: