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

Previous Next

Full log

Message #14 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 19:41:09 +0200

> From: Andreas Schwab <schwab <at> linux-m68k.org>
> Date: Sun, 03 Nov 2013 07:37:04 +0100
> Cc: 15794 <at> debbugs.gnu.org
> 
> Barry OReilly <gundaetiapo <at> gmail.com> writes:
> 
> > #60 0x00000000004ecaa5 in deliver_process_signal (sig=15, handler=0x4ebc30 <handle_fatal_signal>) at sysdep.c:1597
> >         old_errno = 11
> >         on_main_thread = true
> > #61 <signal handler called>
> > No symbol table info available.
> > #62 string_intervals (s=57280353) at lisp.h:3129
> > No locals.
> > #63 mark_object (arg=<optimized out>) at alloc.c:5957
> >         ptr = <optimized out>
> >         ptrx = <optimized out>
> >         obj = 59121106
> >         cdr_count = 0
> 
> 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?

Perhaps a better alternative would be to avoid running kill-emacs-hook
in this case?

Previous Next

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