From 9bd4c3ad3e747a187315a820651fa9c20e7ce552 Mon Sep 17 00:00:00 2001 From: Luc Teirlinck Date: Fri, 10 Jun 2005 15:43:48 +0000 Subject: (Error Debugging): Minor rewording. (Function Debugging): FUNCTION-NAME arg to `cancel-debug-on-entry' is optional. --- lispref/debugging.texi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'lispref/debugging.texi') diff --git a/lispref/debugging.texi b/lispref/debugging.texi index 07dfe18f283..ff9e90f7747 100644 --- a/lispref/debugging.texi +++ b/lispref/debugging.texi @@ -118,8 +118,8 @@ the error. The easiest way is usually to set @end defopt @defopt eval-expression-debug-on-error -If you set this variable to a non-@code{nil} value, then -@code{debug-on-error} will be set to @code{t} when evaluating with the +If this variable has a non-@code{nil} value, then +@code{debug-on-error} is set to @code{t} when evaluating with the command @code{eval-expression}. If @code{eval-expression-debug-on-error} is @code{nil}, then the value of @code{debug-on-error} is not changed. @xref{Lisp Eval,, Evaluating @@ -267,11 +267,11 @@ Debugger entered--entering a function: @end example @end deffn -@deffn Command cancel-debug-on-entry function-name +@deffn Command cancel-debug-on-entry &optional function-name This function undoes the effect of @code{debug-on-entry} on @var{function-name}. When called interactively, it prompts for @var{function-name} in the minibuffer. If @var{function-name} is -@code{nil} or the empty string, it cancels break-on-entry for all +omitted, @code{nil}, or the empty string, it cancels break-on-entry for all functions. Calling @code{cancel-debug-on-entry} does nothing to a function which is -- cgit v1.2.1 From 9edbd0074e6117b4171f9e2289742a9834d6f5a8 Mon Sep 17 00:00:00 2001 From: Luc Teirlinck Date: Sat, 11 Jun 2005 23:42:13 +0000 Subject: (Function Debugging): Delete mention of empty string argument to `cancel-debug-on-entry'. Delete inaccurate description of the return value of that command. --- lispref/debugging.texi | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) (limited to 'lispref/debugging.texi') diff --git a/lispref/debugging.texi b/lispref/debugging.texi index ff9e90f7747..ae3fbdbb480 100644 --- a/lispref/debugging.texi +++ b/lispref/debugging.texi @@ -271,12 +271,9 @@ Debugger entered--entering a function: This function undoes the effect of @code{debug-on-entry} on @var{function-name}. When called interactively, it prompts for @var{function-name} in the minibuffer. If @var{function-name} is -omitted, @code{nil}, or the empty string, it cancels break-on-entry for all -functions. - +omitted or @code{nil}, it cancels break-on-entry for all functions. Calling @code{cancel-debug-on-entry} does nothing to a function which is -not currently set up to break on entry. It always returns -@var{function-name}. +not currently set up to break on entry. @end deffn @node Explicit Debug -- cgit v1.2.1 From cf02d3ed214a099fa56b4007d472d69e46411de0 Mon Sep 17 00:00:00 2001 From: Lute Kamstra Date: Tue, 14 Jun 2005 11:36:41 +0000 Subject: (Function Debugging): Primitives can break on entry too. --- lispref/debugging.texi | 22 +++++++++++++--------- 1 file changed, 13 insertions(+), 9 deletions(-) (limited to 'lispref/debugging.texi') diff --git a/lispref/debugging.texi b/lispref/debugging.texi index ae3fbdbb480..739dd1fe298 100644 --- a/lispref/debugging.texi +++ b/lispref/debugging.texi @@ -210,15 +210,19 @@ called shortly before the problem, step quickly over the call to that function, and then step through its caller. @deffn Command debug-on-entry function-name -This function requests @var{function-name} to invoke the debugger each time -it is called. It works by inserting the form @code{(debug 'debug)} into -the function definition as the first form. - -Any function defined as Lisp code may be set to break on entry, -regardless of whether it is interpreted code or compiled code. If the -function is a command, it will enter the debugger when called from Lisp -and when called interactively (after the reading of the arguments). You -can't debug primitive functions (i.e., those written in C) this way. +This function requests @var{function-name} to invoke the debugger each +time it is called. It works by inserting the form +@code{(implement-debug-on-entry)} into the function definition as the +first form. + +Any function or macro defined as Lisp code may be set to break on +entry, regardless of whether it is interpreted code or compiled code. +If the function is a command, it will enter the debugger when called +from Lisp and when called interactively (after the reading of the +arguments). You can also set debug-on-entry for primitive functions +(i.e., those written in C) this way, but it only takes effect when the +primitive is called from Lisp code. Debug-on-entry is not allowed for +special forms. When @code{debug-on-entry} is called interactively, it prompts for @var{function-name} in the minibuffer. If the function is already set -- cgit v1.2.1