From: Eli Zaretskii <eliz@gnu.org>
To: Barry OReilly <gundaetiapo@gmail.com>
Cc: schwab@suse.de, 15794@debbugs.gnu.org
Subject: bug#15794: Core dump after SIGTERM during GC marking
Date: Tue, 05 Nov 2013 17:53:17 +0200 [thread overview]
Message-ID: <83bo1y976a.fsf@gnu.org> (raw)
In-Reply-To: <CAFM41H2pxb+CziJJfzw9vMbXkURm0Tbn0gH=TwjjaUp=CwBBaw@mail.gmail.com>
> Date: Tue, 5 Nov 2013 10:27:32 -0500
> From: Barry OReilly <gundaetiapo@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 15794 <15794@debbugs.gnu.org>
>
> I then started Emacs via GDB and issued a SIGTERM during the sleep. As
> before, I witnessed an abort in a kill hook. The C and Lisp
> backtraces:
Thanks. But the Lisp backtrace doesn't tell which function of the
kill-emacs-hook was running, and the C backtrace is different (no
trace of regexp functions) anyway, and GC didn't really start doing
its job, so it's not exactly the same crash.
To try and see which function from those that are in kill-emacs-hook,
go to frame #68:
> #68 0x0000000000586c85 in Frun_hooks (nargs=1, args=0xbd2200) at eval.c:2367
> #69 0x00000000005031d5 in Fkill_emacs (arg=60) at emacs.c:1891
> #70 0x0000000000503300 in terminate_due_to_signal (sig=15,
> backtrace_limit=40) at emacs.c:359
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.
If you cannot do this in frame 68 for some reason (yours is an
optimized build, so variables might not reflect the true state of
affairs), try the frame above it:
> #67 0x0000000000586be0 in run_hook_with_args (nargs=1, args=0x7fffffff9e60,
> funcall=0x589a60 <funcall_nil>) at eval.c:2525
Again, look at 'args'.
Btw, I'm not sure what we are trying to establish here. Shutting down
Emacs in the middle of GC is inherently dangerous.
next prev parent reply other threads:[~2013-11-05 15:53 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 [this message]
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=83bo1y976a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15794@debbugs.gnu.org \
--cc=gundaetiapo@gmail.com \
--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).