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

Previous Next

Package: emacs;

Reported by: Barry OReilly <gundaetiapo <at> gmail.com>

Date: Sun, 3 Nov 2013 04:30:03 UTC

Severity: normal

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

Message #20 received at 15794 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: 15794 <at> debbugs.gnu.org, gundaetiapo <at> gmail.com
Subject: Re: bug#15794: Core dump after SIGTERM during GC marking
Date: Sun, 03 Nov 2013 21:52:25 +0200

> From: Andreas Schwab <schwab <at> linux-m68k.org>
> Cc: 15794 <at> debbugs.gnu.org,  gundaetiapo <at> 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.
This bug report was last modified 5 years and 289 days ago.

Previous Next

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