From: Paul Pogonyshev <pogonyshev@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33034@debbugs.gnu.org
Subject: bug#33034: `unwind-protect' cleanup form is not executed if body dies in stack overflow
Date: Sat, 13 Oct 2018 13:38:11 +0200 [thread overview]
Message-ID: <CAG7BparammrMeo1H4O16snVmVVzHdgXtw9ygkX0z5xr2FfzYbg@mail.gmail.com> (raw)
In-Reply-To: <83efcuulsa.fsf@gnu.org>
OK, but why does it hit the limit? Logically, by the time cleanup form
is called, all the (overflow) stack frames should be removed and the
cleanup form should see practically empty stack. It shouldn't be much
different from calling cleanup without overflowing the stack to begin
with.
Paul
On Sat, 13 Oct 2018 at 13:30, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Date: Sat, 13 Oct 2018 14:01:00 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> > Cc: 33034@debbugs.gnu.org
> >
> > > I haven't looked into the source code, but it seems that these
> > > examples don't involve C-level stack overflow.
> >
> > You are right, this issue is unrelated to C stack overflow.
>
> What actually happens here is that the cleanup form _is_ called, but
> it again hits the limit of Lisp local bindings, and therefore itself
> signals an error. And unwind-protect does not protect cleanup forms
> (this is documented).
next prev parent reply other threads:[~2018-10-13 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 10:07 bug#33034: `unwind-protect' cleanup form is not executed if body dies in stack overflow Paul Pogonyshev
2018-10-13 10:29 ` Eli Zaretskii
2018-10-13 10:35 ` Paul Pogonyshev
2018-10-13 10:45 ` Eli Zaretskii
2018-10-13 10:52 ` Paul Pogonyshev
2018-10-13 11:01 ` Eli Zaretskii
2018-10-13 11:29 ` Eli Zaretskii
2018-10-13 11:38 ` Paul Pogonyshev [this message]
2018-10-13 12:35 ` Eli Zaretskii
2018-10-13 14:02 ` Paul Pogonyshev
2018-10-14 17:02 ` Paul Eggert
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=CAG7BparammrMeo1H4O16snVmVVzHdgXtw9ygkX0z5xr2FfzYbg@mail.gmail.com \
--to=pogonyshev@gmail.com \
--cc=33034@debbugs.gnu.org \
--cc=eliz@gnu.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).