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

Previous Next

Full log

View this message in rfc822 format

From: Barry OReilly <gundaetiapo <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Andreas Schwab <schwab <at> suse.de>, 15794 <15794 <at> debbugs.gnu.org>
Subject: bug#15794: Core dump after SIGTERM during GC marking
Date: Tue, 5 Nov 2013 11:52:09 -0500

[Message part 1 (text/plain, inline)]

Since I can't reproduce the original crash, I am trying other means of
gathering evidence. A SIGTERM could be handled at any time right?
Including as in this artificial reproduction.

> But the Lisp backtrace doesn't tell which function of the
> kill-emacs-hook was running,

Yes it does. The hook is ede-save-cache. It is one of the two hooks my
configuration sets up, as I indicated earlier.

> and GC didn't really start doing its job, so it's not exactly the
> same crash.

It is after gc_in_progress = 1. Are you trying to argue Emacs cannot
possibly enter the SIGTERM handler between that and when GC "really
starts doing its job" (whenever that is)?

> And look at the variable 'args', which should be a list. Since this
> session crashed in GC, it is not safe to print Lisp objects with
> "pp" and its likes. Instead, you will have to walk the list using
> "xcar" and "xcdr", display the type of each object in the list using
> "xtype", and then display the object itself with the appropriate x*
> command, normally "xsymbol", since the list is constructed from
> function symbols.

Can this be done for core dump files?

[Message part 2 (text/html, inline)]

Previous Next

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