[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
debugging.texi
From: |
Luc Teirlinck |
Subject: |
debugging.texi |
Date: |
Wed, 15 Jun 2005 13:50:08 -0500 (CDT) |
What about the following additional change to debugging.texi? It may
not be that surprising that if you can not step through a
byte-compiled function, you can not step through a primitive function
either, but it may not hurt to explicitly mention it.
I can install if desired.
===File ~/debugging.texi-diff===============================
*** debugging.texi 14 Jun 2005 08:19:54 -0500 1.32
--- debugging.texi 15 Jun 2005 13:33:13 -0500
***************
*** 350,356 ****
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:
--- 350,357 ----
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.) There is no way to step through
! a primitive function.
Here is a list of Debugger mode commands:
============================================================
Re: debugging.texi, Richard Stallman, 2005/06/11
- debugging.texi,
Luc Teirlinck <=