Mercurial > emacs
changeset 55734:93c897de7898
(Eval): Increasing max-lisp-eval-depth can cause real stack overflow.
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Sat, 22 May 2004 21:59:46 +0000 |
| parents | 8b5d63bbe285 |
| children | 1874eee23678 |
| files | lispref/eval.texi |
| diffstat | 1 files changed, 6 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/lispref/eval.texi Sat May 22 21:58:24 2004 +0000 +++ b/lispref/eval.texi Sat May 22 21:59:46 2004 +0000 @@ -678,9 +678,12 @@ @defvar max-lisp-eval-depth This variable defines the maximum depth allowed in calls to @code{eval}, @code{apply}, and @code{funcall} before an error is signaled (with error -message @code{"Lisp nesting exceeds max-lisp-eval-depth"}). This limit, -with the associated error when it is exceeded, is one way that Lisp -avoids infinite recursion on an ill-defined function. +message @code{"Lisp nesting exceeds max-lisp-eval-depth"}). + +This limit, with the associated error when it is exceeded, is one way +Emacs Lisp avoids infinite recursion on an ill-defined function. If +you increase the value of @code{max-lisp-eval-depth} too much, such +code can cause stack overflow instead. @cindex Lisp nesting error The depth limit counts internal uses of @code{eval}, @code{apply}, and