From: Noam Postavsky <npostavs@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 30675@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#30675: Ask the user what to do when shr-make-table: Variable binding depth exceeds max-specpdl-size
Date: Fri, 13 Apr 2018 08:15:53 -0400 [thread overview]
Message-ID: <87zi27jo92.fsf@gmail.com> (raw)
In-Reply-To: <87fu3z9vjt.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Fri, 13 Apr 2018 13:48:22 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Hm... On what architectures is there a potential for a C stack
> overflow? I thought that these days, C stack overflows basically didn't
> happened, and we only had the max-specpdl-size as a sanity check to
> avoid deep lisp backtraces and stuff, but I may well have misunderstood
> things.
The default stack size soft ulimit on GNU/Linux seems to be 8MB, Emacs
tries to increase the limit by some fixed amount. It can be set to
unlimited (I wouldn't expect most users to do that though). On macOS,
there seems to be a hard limit of 64MB, so setting to unlimited doesn't
work.
Recent changes to Emacs have caused `read' to use more stack space, so
it's definitely possible to hit the limits when reading a deeply nested
structure (see bugs #27571 and #27779). Not sure how likely it is when
reading deeply nested HTML, but I'm sure if you increase
max-specpdl-size enough with the right HTML page you can manage it :)
next prev parent reply other threads:[~2018-04-13 12:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877eqwbqvc.fsf@jidanni.org>
[not found] ` <b4mfu5kk0iz.fsf@jpl.org>
2018-03-02 2:40 ` bug#30675: Ask the user what to do when shr-make-table: Variable binding depth exceeds max-specpdl-size 積丹尼 Dan Jacobson
2018-03-02 2:51 ` Noam Postavsky
2018-04-12 23:49 ` Lars Ingebrigtsen
2018-04-13 0:06 ` 積丹尼 Dan Jacobson
2018-04-13 0:27 ` Lars Ingebrigtsen
2018-04-13 9:29 ` Eli Zaretskii
2018-04-13 11:48 ` Lars Ingebrigtsen
2018-04-13 12:15 ` Noam Postavsky [this message]
2018-04-13 12:32 ` Lars Ingebrigtsen
2018-04-13 12:43 ` Eli Zaretskii
2018-04-13 15:34 ` Lars Ingebrigtsen
2018-04-15 17:02 ` Lars Ingebrigtsen
2018-04-13 12:40 ` 積丹尼 Dan Jacobson
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=87zi27jo92.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=30675@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
/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).