aboutsummaryrefslogtreecommitdiffstats
path: root/lispref/debugging.texi
diff options
context:
space:
mode:
authorLuc Teirlinck2005-06-16 20:06:48 +0000
committerLuc Teirlinck2005-06-16 20:06:48 +0000
commit12f0e0436a6f466e96de7f130c4d422c3b1b2006 (patch)
tree4a646e267d5afff7f70e388c8bc963089286e5e4 /lispref/debugging.texi
parent246d1dba8dedf0a3548eb13d9fdd793f1f2a9e3b (diff)
downloademacs-12f0e0436a6f466e96de7f130c4d422c3b1b2006.tar.gz
emacs-12f0e0436a6f466e96de7f130c4d422c3b1b2006.zip
(Debugger Commands): Mention that the Lisp debugger can not step
through primitive functions.
Diffstat (limited to 'lispref/debugging.texi')
-rw-r--r--lispref/debugging.texi3
1 files changed, 2 insertions, 1 deletions
diff --git a/lispref/debugging.texi b/lispref/debugging.texi
index 739dd1fe298..75be0462d66 100644
--- a/lispref/debugging.texi
+++ b/lispref/debugging.texi
@@ -350,7 +350,8 @@ structures of an interpreted function, but cannot do so in a
350byte-compiled function. If you would like to step through a 350byte-compiled function. If you would like to step through a
351byte-compiled function, replace it with an interpreted definition of 351byte-compiled function, replace it with an interpreted definition of
352the same function. (To do this, visit the source for the function and 352the same function. (To do this, visit the source for the function and
353type @kbd{C-M-x} on its definition.) 353type @kbd{C-M-x} on its definition.) You can not use the Lisp debugger
354to step through a primitive function.
354 355
355 Here is a list of Debugger mode commands: 356 Here is a list of Debugger mode commands:
356 357