From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: 15794@debbugs.gnu.org, gundaetiapo@gmail.com
Subject: bug#15794: Core dump after SIGTERM during GC marking
Date: Mon, 04 Nov 2013 18:02:38 +0200 [thread overview]
Message-ID: <83y554889t.fsf@gnu.org> (raw)
In-Reply-To: <mvmtxfswnn7.fsf@hawking.suse.de>
> 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
http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html
seems to agree.
next prev parent reply other threads:[~2013-11-04 16:02 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
2013-11-04 3:38 ` Eli Zaretskii
2013-11-04 8:56 ` Andreas Schwab
2013-11-04 16:02 ` Eli Zaretskii [this message]
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=83y554889t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15794@debbugs.gnu.org \
--cc=gundaetiapo@gmail.com \
--cc=schwab@suse.de \
/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).