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 12:35:46 +0200 [thread overview]
Message-ID: <CAG7BpaqhqsCQT_8Zoyge2Y_70f3rgHJT-NpR=bHVjYv5_KAXkA@mail.gmail.com> (raw)
In-Reply-To: <83k1mmuoli.fsf@gnu.org>
I see. Wonderful approach. At least I'm not supposed to restart my machine.
On Sat, 13 Oct 2018 at 12:29, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Paul Pogonyshev <pogonyshev@gmail.com>
> > Date: Sat, 13 Oct 2018 12:07:48 +0200
> >
> > To reproduce:
> >
> > (defun overflow ()
> > (overflow))
> > (defun test ()
> > (interactive)
> > (message "BEFORE")
> > (unwind-protect
> > (overflow)
> > (message "CLEANUP")))
> >
> > Invocation of `test' never issues message "CLEANUP", whether it is run
> > interactively or non-interactively.
>
> You are not supposed to continue using Emacs as usual after it
> recovered from a C stack overflow. You are supposed to exit Emacs and
> restart the session.
>
> The C stack overflow recovery is provided to allow you to save your
> edits instead of losing them.
>
> P.S. I was somehow certain that we say the above somewhere in the
> docs, but I cannot find it, so maybe I was dreaming. Patches to add
> that are welcome.
next prev parent reply other threads:[~2018-10-13 10:35 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 [this message]
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
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='CAG7BpaqhqsCQT_8Zoyge2Y_70f3rgHJT-NpR=bHVjYv5_KAXkA@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).