GNU bug report logs - #15794
Core dump after SIGTERM during GC marking

Previous Next

Full log

View this message in rfc822 format

From: Andreas Schwab <schwab <at> suse.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 15794 <at> debbugs.gnu.org, gundaetiapo <at> gmail.com
Subject: bug#15794: Core dump after SIGTERM during GC marking
Date: Mon, 04 Nov 2013 17:18:41 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Andreas Schwab <schwab <at> suse.de>
>> Cc: 15794 <at> debbugs.gnu.org, gundaetiapo <at> gmail.com
>> Date: Mon, 04 Nov 2013 09:56:44 +0100
>> 
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>> 
>> >> From: Andreas Schwab <schwab <at> linux-m68k.org>
>> >> Cc: 15794 <at> debbugs.gnu.org,  gundaetiapo <at> 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 <at> suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.