From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 15794@debbugs.gnu.org, gundaetiapo@gmail.com
Subject: bug#15794: Core dump after SIGTERM during GC marking
Date: Sun, 03 Nov 2013 19:41:09 +0200 [thread overview]
Message-ID: <83d2mh9ydm.fsf@gnu.org> (raw)
In-Reply-To: <87k3gq2dpr.fsf@igel.home>
> From: Andreas Schwab <schwab@linux-m68k.org>
> Date: Sun, 03 Nov 2013 07:37:04 +0100
> Cc: 15794@debbugs.gnu.org
>
> Barry OReilly <gundaetiapo@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?
next prev parent reply other threads:[~2013-11-03 17:41 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 [this message]
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
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=83d2mh9ydm.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).