316 |
considered the @dfn{current frame}. Some of the debugger commands |
considered the @dfn{current frame}. Some of the debugger commands |
317 |
operate on the current frame. |
operate on the current frame. |
318 |
|
|
319 |
|
If a function name is underlined, that means the debugger knows |
320 |
|
where its source code is located. You can click @kbd{Mouse-2} on that |
321 |
|
name, or move to it and type @key{RET}, to visit the source code. |
322 |
|
|
323 |
The debugger itself must be run byte-compiled, since it makes |
The debugger itself must be run byte-compiled, since it makes |
324 |
assumptions about how many stack frames are used for the debugger |
assumptions about how many stack frames are used for the debugger |
325 |
itself. These assumptions are false if the debugger is running |
itself. These assumptions are false if the debugger is running |
331 |
@subsection Debugger Commands |
@subsection Debugger Commands |
332 |
@cindex debugger command list |
@cindex debugger command list |
333 |
|
|
334 |
Inside the debugger (in Debugger mode), these special commands are |
The debugger buffer (in Debugger mode) provides special commands in |
335 |
available in addition to the usual cursor motion commands. (Keep in |
addition to the usual Emacs commands. The most important use of |
336 |
mind that all the usual facilities of Emacs, such as switching windows |
debugger commands is for stepping through code, so that you can see |
337 |
or buffers, are still available.) |
how control flows. The debugger can step through the control |
338 |
|
structures of an interpreted function, but cannot do so in a |
339 |
The most important use of debugger commands is for stepping through |
byte-compiled function. If you would like to step through a |
340 |
code, so that you can see how control flows. The debugger can step |
byte-compiled function, replace it with an interpreted definition of |
341 |
through the control structures of an interpreted function, but cannot do |
the same function. (To do this, visit the source for the function and |
342 |
so in a byte-compiled function. If you would like to step through a |
type @kbd{C-M-x} on its definition.) |
|
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.) |
|
343 |
|
|
344 |
Here is a list of Debugger mode commands: |
Here is a list of Debugger mode commands: |
345 |
|
|