[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#15794: Core dump after SIGTERM during GC marking
From: |
Eli Zaretskii |
Subject: |
bug#15794: Core dump after SIGTERM during GC marking |
Date: |
Sun, 03 Nov 2013 21:52:25 +0200 |
> 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.
Not to mention that Emacs has been doing this for many years, and that
it's a valuable feature that it does.
- bug#15794: Core dump after SIGTERM during GC marking, Barry OReilly, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Andreas Schwab, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Eli Zaretskii, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Andreas Schwab, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Eli Zaretskii, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Andreas Schwab, 2013/11/04
- bug#15794: Core dump after SIGTERM during GC marking, Eli Zaretskii, 2013/11/04
- bug#15794: Core dump after SIGTERM during GC marking, Andreas Schwab, 2013/11/04
- bug#15794: Core dump after SIGTERM during GC marking, Barry OReilly, 2013/11/05
- bug#15794: Core dump after SIGTERM during GC marking, Eli Zaretskii, 2013/11/05