Re: debugging.texi

[Richard Stallman <rms@gnu.org>]

      (defun debug-on-entry (function)
	"Request FUNCTION to invoke debugger each time it is called.
    + When called interactively, prompt for FUNCTION in the minibuffer.

That is useful to add.

      If you tell the debugger to continue, FUNCTION's execution proceeds.
      This works by modifying the definition of FUNCTION,
      which must be written in Lisp, not predefined.
      Use \\[cancel-debug-on-entry] to cancel the effect of this command.
    ! Redefining FUNCTION also cancels it.  This command returns FUNCTION."

There's no need for that change.

      (defun cancel-debug-on-entry (&optional function)
	"Undo effect of \\[debug-on-entry] on FUNCTION.
    ! If argument is nil or an empty string, cancel for all functions.
    ! When called interactively, prompt for FUNCTION in the minibuffer.
    ! To specify a nil argument interactively, exit with an empty minibuffer.

That is useful.

    ! 
    ! If specified, FUNCTION must be a symbol with a function definition,
    ! nil, or an empty string.  If FUNCTION is a non-nil symbol with
    ! a function definition, the return value is FUNCTION, even if FUNCTION
    ! was not previously set up to break on entry.  If FUNCTION is omitted,
    ! nil, or an empty string the return value is a list of all functions
    ! for which break-on-entry was canceled."

That is not needed.