GNU bug report logs - #31919
26.1.50; Lisp Debugger doesn't work when at stack limit

Previous Next

Full log

Message #17 received at 31919 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gemini Lasswell <gazally <at> runbox.com>
Cc: 31919 <at> debbugs.gnu.org
Subject: Re: bug#31919: 26.1.50; Lisp Debugger doesn't work when at stack limit
Date: Sat, 30 Jun 2018 12:39:32 +0300

> From: Gemini Lasswell <gazally <at> runbox.com>
> Cc: 31919 <at> debbugs.gnu.org
> Date: Wed, 27 Jun 2018 21:26:12 -0700
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Yes, but please add a comment there describing the reason.  How much
> > more depth out of 40 is actually needed to allow cl-print calls, and
> > how much is safety margin?
> 
> I determined by experiment that 77 needs to be added to
> max-lisp-eval-depth to permit the debugger to print
> ((1 (2 (3 (4 (5 (6 (7 (8))))))))).  So I changed the increment to 100.
> But I really have no idea what is reasonable for a safety margin.
> Here's a new patch with comments.

Thanks, this LGTM for emacs-26.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.