unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Browne <cbbrowne@afilias.info>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 8764@debbugs.gnu.org
Subject: bug#8764: 24.0.50; cedet/semantic/bovine/c-by.el:184:1:Error: Lisp nesting exceeds `max-lisp-eval-depth'
Date: Mon, 30 May 2011 15:19:30 -0400	[thread overview]
Message-ID: <BANLkTi=7A-r9DgS1dg7vdqKQHu_f=UymkQ@mail.gmail.com> (raw)
In-Reply-To: <jwvboykypv1.fsf-monnier+emacs@gnu.org>

On Mon, May 30, 2011 at 3:04 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> The problem isn't within the running Emacs process, rather it's with the
>> build process for trunk.
>
> It's a file that requires a lot of stack depth, indeed.
>
>> I'm not sure where to proceed from here.  The default value is 600; I
>> don't know if fiddling that higher would actually help.
>
> The lisp/Makefile.in pushes it up to 1200 and AFAIK this is sufficient
> to bootstrap.  But maybe there are cases where a recompile ends up
> recompiling in a different order and so more of the files are still
> uncompiled, thus needing more stack space.

Thanks for pointing out the location; I did a bit of "iterative
refinement" and found that 1635 was sufficient whilst 1625 failed.

That isn't quite a scientific evaluation of what ought to be
necessary, but it sure seems that the value can need to be higher than
1200, and it's pretty plausible that 1635 only helps until an extra
couple elements get added to the parser, increasing stack usage.





  reply	other threads:[~2011-05-30 19:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30 16:56 bug#8764: 24.0.50; cedet/semantic/bovine/c-by.el:184:1:Error: Lisp nesting exceeds `max-lisp-eval-depth' Christopher Browne
2011-05-30 19:01 ` David Engster
2011-05-30 22:14   ` Stefan Monnier
2011-05-30 22:50     ` Stefan Monnier
2011-05-30 19:04 ` Stefan Monnier
2011-05-30 19:19   ` Christopher Browne [this message]
2011-05-30 22:15     ` Stefan Monnier
2014-02-03 23:48       ` Lars Ingebrigtsen
2021-11-05 19:10 ` bug#8764: " Paul Eggert
2021-12-03 21:20   ` bug#8764: 24.0.50; " Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to='BANLkTi=7A-r9DgS1dg7vdqKQHu_f=UymkQ@mail.gmail.com' \
    --to=cbbrowne@afilias.info \
    --cc=8764@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).