all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: 31793@debbugs.gnu.org, sdl.web@gmail.com
Subject: bug#31793: 26.1; (error "Lisp nesting exceeds	‘max-lisp-eval-depth’")
Date: Tue, 12 Jun 2018 08:21:27 +0300	[thread overview]
Message-ID: <99D8E495-B396-4266-8BF1-BA0B609DEC3D@gnu.org> (raw)
In-Reply-To: <m11sdc7g7f.fsf@gmail.com>

On June 12, 2018 7:59:32 AM GMT+03:00, Leo Liu <sdl.web@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.





  reply	other threads:[~2018-06-12  5:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12  2:32 bug#31793: 26.1; (error "Lisp nesting exceeds ‘max-lisp-eval-depth’") Leo Liu
2018-06-12  4:43 ` Leo Liu
2018-06-12  4:59   ` Leo Liu
2018-06-12  5:21     ` Eli Zaretskii [this message]
2018-06-12  8:46       ` Leo Liu
2018-06-23 15:47         ` John Shahid
2018-06-24  8:27           ` Leo Liu
2018-06-25 13:59             ` John Shahid
2018-06-25 16:24             ` Noam Postavsky
2018-07-03 16:43           ` John Shahid
2018-07-04 22:38             ` Noam Postavsky
2018-07-05 13:59               ` Eli Zaretskii
2018-07-05 16:33                 ` John Shahid
2018-07-10 12:17                   ` Noam Postavsky
2018-06-12  5:04   ` Eli Zaretskii
2018-06-12  5:24     ` Leo Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=99D8E495-B396-4266-8BF1-BA0B609DEC3D@gnu.org \
    --to=eliz@gnu.org \
    --cc=31793@debbugs.gnu.org \
    --cc=sdl.web@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.