unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Barry OReilly <gundaetiapo@gmail.com>
Cc: 15794@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#15794: Core dump after SIGTERM during GC marking
Date: Sun, 03 Nov 2013 22:42:15 +0200	[thread overview]
Message-ID: <8338nd9pzs.fsf@gnu.org> (raw)
In-Reply-To: <CAFM41H3a_4=R-QN3CB54joQGAOE1+zaVQvVAAYo_sE4ddgT4gQ@mail.gmail.com>

> Date: Sun, 3 Nov 2013 15:29:55 -0500
> From: Barry OReilly <gundaetiapo@gmail.com>
> Cc: Andreas Schwab <schwab@linux-m68k.org>, 15794@debbugs.gnu.org
> 
> (gdb) xbacktrace
> You can't do that without a process to debug.

Sorry, I failed to mention that xbacktrace won't work on a core dump.

But you should be able to display the value of kill-emacs-hook, by
walking its car and cdr links.





  parent reply	other threads:[~2013-11-03 20:42 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 [this message]
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
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=8338nd9pzs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=15794@debbugs.gnu.org \
    --cc=gundaetiapo@gmail.com \
    --cc=schwab@linux-m68k.org \
    /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).