From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15794@debbugs.gnu.org, gundaetiapo@gmail.com
Subject: bug#15794: Core dump after SIGTERM during GC marking
Date: Sun, 03 Nov 2013 23:22:31 +0100 [thread overview]
Message-ID: <8738nd2kig.fsf@igel.home> (raw)
In-Reply-To: <83a9hl9sau.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 03 Nov 2013 21:52:25 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andreas Schwab <schwab@linux-m68k.org>
>> Cc: 15794@debbugs.gnu.org, gundaetiapo@gmail.com
>> Date: Sun, 03 Nov 2013 19:03:00 +0100
>>
>> >> The signal was received during GC. Shouldn't its handling be postponed
>> >> then?
>> >
>> > Maybe. But then it would be impossible to kill Emacs during a runaway
>> > GC in a way that would cause Emacs to auto-save, wouldn't it?
>>
>> Even auto-save is a no-no in a signal handler.
>
> I don't see why. Auto-save takes care to do only predictable things.
A lot of things that are a no-no in a signal handler, like calling
auto-save-hook.
> Not to mention that Emacs has been doing this for many years, and that
> it's a valuable feature that it does.
That's the nice thing about undefined behaviour, it can take a long time
until you see its ugly head.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-11-03 22:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 4:28 bug#15794: Core dump after SIGTERM during GC marking Barry OReilly
2013-11-03 6:37 ` Andreas Schwab
2013-11-03 17:41 ` Eli Zaretskii
2013-11-03 18:03 ` Andreas Schwab
2013-11-03 19:52 ` Eli Zaretskii
2013-11-03 20:29 ` Barry OReilly
2013-11-03 20:39 ` Eli Zaretskii
2013-11-03 20:42 ` Eli Zaretskii
2013-11-03 22:22 ` Andreas Schwab [this message]
2013-11-04 3:38 ` Eli Zaretskii
2013-11-04 8:56 ` Andreas Schwab
2013-11-04 16:02 ` Eli Zaretskii
2013-11-04 16:18 ` Andreas Schwab
2013-11-05 15:27 ` Barry OReilly
2013-11-05 15:53 ` Eli Zaretskii
2013-11-05 16:52 ` Barry OReilly
2013-11-05 17:16 ` Eli Zaretskii
2019-09-29 14:00 ` Lars Ingebrigtsen
2013-11-03 17:39 ` Eli Zaretskii
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=8738nd2kig.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=15794@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gundaetiapo@gmail.com \
/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).