From: Richard M. Stallman Date: Sat, 22 May 2004 21:59:46 +0000 (+0000) Subject: (Eval): Increasing max-lisp-eval-depth can cause real stack overflow. X-Git-Tag: ttn-vms-21-2-B4~6100 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=0df043a7066c4dd6ef093b83ec04973ace516a91;p=emacs.git (Eval): Increasing max-lisp-eval-depth can cause real stack overflow. --- diff --git a/lispref/eval.texi b/lispref/eval.texi index 7d1ebb9d307..3c8a7a5e8a3 100644 --- a/lispref/eval.texi +++ b/lispref/eval.texi @@ -678,9 +678,12 @@ output of the output functions is printed in the echo area. @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