bug#15794: Core dump after SIGTERM during GC marking

[Andreas Schwab]

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."