bug#15794: Core dump after SIGTERM during GC marking

[Andreas Schwab]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andreas Schwab <schwab@suse.de>
>> Cc: 15794@debbugs.gnu.org, gundaetiapo@gmail.com
>> Date: Mon, 04 Nov 2013 09:56:44 +0100
>> 
>> 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 23:22:31 +0100
>> >> 
>> >> >> 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.
>> >
>> > We could disable that (and the other things) as well.
>> 
>> You would have to disable opening files, too.
>
> What's wrong with opening files from a signal handler?  I always
> thought that open(2) (and also write(2) and close(2)) are async-signal
> safe on Posix systems, and this page

But fdopen isn't.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."