summaryrefslogtreecommitdiff
path: root/lispref/debugging.texi
diff options
context:
space:
mode:
authorLuc Teirlinck <teirllm@auburn.edu>2005-06-16 20:06:48 +0000
committerLuc Teirlinck <teirllm@auburn.edu>2005-06-16 20:06:48 +0000
commit12f0e0436a6f466e96de7f130c4d422c3b1b2006 (patch)
tree4a646e267d5afff7f70e388c8bc963089286e5e4 /lispref/debugging.texi
parent246d1dba8dedf0a3548eb13d9fdd793f1f2a9e3b (diff)
(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 739dd1fe29..75be0462d6 100644
--- a/lispref/debugging.texi
+++ b/lispref/debugging.texi
@@ -350,7 +350,8 @@ 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.)
+type @kbd{C-M-x} on its definition.) You can not use the Lisp debugger
+to step through a primitive function.
Here is a list of Debugger mode commands: