From: Barry OReilly <gundaetiapo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andreas Schwab <schwab@suse.de>, 15794 <15794@debbugs.gnu.org>
Subject: bug#15794: Core dump after SIGTERM during GC marking
Date: Tue, 5 Nov 2013 11:52:09 -0500 [thread overview]
Message-ID: <CAFM41H0vqf3myAYcGmSqLg-6woL20yU-h7N43F4XEddm4i396Q@mail.gmail.com> (raw)
In-Reply-To: <83bo1y976a.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
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?
[-- Attachment #2: Type: text/html, Size: 1361 bytes --]
next prev parent reply other threads:[~2013-11-05 16:52 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
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 [this message]
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=CAFM41H0vqf3myAYcGmSqLg-6woL20yU-h7N43F4XEddm4i396Q@mail.gmail.com \
--to=gundaetiapo@gmail.com \
--cc=15794@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).