From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: schwab@suse.de, Barry OReilly <gundaetiapo@gmail.com>,
15794@debbugs.gnu.org
Subject: bug#15794: Core dump after SIGTERM during GC marking
Date: Sun, 29 Sep 2019 16:00:50 +0200 [thread overview]
Message-ID: <87impbjj71.fsf@gnus.org> (raw)
In-Reply-To: <83y5527oqk.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 05 Nov 2013 19:16:51 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Btw, if you want to see a better backtrace, both in C and in Lisp,
> remove or rename the *.elc files of the involved packages. then Emacs
> will run the *.el files in the interpreter, and you will see much more
> detail, instead of all those unhelpful exec_byte_code calls that tell
> nothing about what is being invoked.
This was five years ago, and much has changed in this area since that
time, so I doubt that we'll be able to make further progress with this
bug report, and I'm closing it. Please reopen if this problem is still
an issue.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-29 14:00 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
2013-11-05 17:16 ` Eli Zaretskii
2019-09-29 14:00 ` Lars Ingebrigtsen [this message]
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=87impbjj71.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=15794@debbugs.gnu.org \
--cc=eliz@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).