GNU bug report logs - #31793
26.1; (error "Lisp nesting exceeds ‘max-lisp-eval-depth’")

Previous Next

Package: emacs;

Reported by: Leo Liu <sdl.web <at> gmail.com>

Date: Tue, 12 Jun 2018 02:33:02 UTC

Severity: normal

Tags: fixed

Found in version 26.1

Fixed in version 26.2

Done: Noam Postavsky <npostavs <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: bug-gnu-emacs <at> gnu.org,Leo Liu <sdl.web <at> gmail.com>,31793 <at> debbugs.gnu.org
Subject: Re: bug#31793: 26.1; (error "Lisp nesting exceeds	‘max-lisp-eval-depth’")
Date: Tue, 12 Jun 2018 08:21:27 +0300

On June 12, 2018 7:59:32 AM GMT+03:00, Leo Liu <sdl.web <at> gmail.com> wrote:
> On 2018-06-12 12:43 +0800, Leo Liu wrote:
> > Get this same issue a second time also reading in GNUS. I'll have
> the
> > faulty emacs session available for a short while. If someone knows
> how
> > to get more info on what's wrong, I can try and get it.
> 
> The session crashed instead. I was trying to increase max-specpdl-size
> and max-lisp-eval-depth from emacsclient -e. The crash report from the
> OS is attached.

Ugh, macOS...  This means no xbacktrace and no other GDB
wizardry...

Well, I think the most important thing is to produce a Lisp
backtrace from the error.
This bug report was last modified 7 years and 9 days ago.

Previous Next

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