From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 8764@debbugs.gnu.org, Christopher Browne <cbbrowne@afilias.info>
Subject: bug#8764: 24.0.50; cedet/semantic/bovine/c-by.el:184:1:Error: Lisp nesting exceeds `max-lisp-eval-depth'
Date: Mon, 03 Feb 2014 15:48:37 -0800 [thread overview]
Message-ID: <87iosv21wq.fsf@building.gnus.org> (raw)
In-Reply-To: <jwvei3fygwc.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 30 May 2011 19:15:59 -0300")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> 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.
>
> Since 1200 seems sufficient during bootstrap, it would be worthwhile to
> try and figure out what is different between your case and the
> bootstrap case.
More information was requested two years ago, but no further progress
has been made (and this seems to work for everybody else), so I'm
closing this bug report. If this problem is still present, please
reopen the bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2014-02-03 23:48 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
2011-05-30 22:15 ` Stefan Monnier
2014-02-03 23:48 ` Lars Ingebrigtsen [this message]
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=87iosv21wq.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=8764@debbugs.gnu.org \
--cc=cbbrowne@afilias.info \
--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).