From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: adrian@medranocalvo.com, 23912@debbugs.gnu.org
Subject: bug#23912: 25.0.95; Abort in gc when working with streams
Date: Thu, 14 Jul 2016 21:49:26 +0300 [thread overview]
Message-ID: <83shvc6ond.fsf@gnu.org> (raw)
In-Reply-To: <87k2go6pib.fsf@web.de> (message from Michael Heerdegen on Thu, 14 Jul 2016 20:30:52 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Thu, 14 Jul 2016 20:30:52 +0200
> Cc: 23912@debbugs.gnu.org
>
> > Lisp Backtrace:
>
> How can I produce such a lisp backtrace after Emacs has crashed?
Source src/.gdbinit and type "xbacktrace". If you invoke GDB from the
Emacs's src directory, it tries to do that automatically (but recent
GDB versions will by default refuse to do that "for security reasons",
so you will have to customize GDB in your ~/.gdbinit).
next prev parent reply other threads:[~2016-07-14 18:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 16:48 bug#23912: 25.0.95; Abort in gc when working with streams Michael Heerdegen
2016-07-07 17:15 ` Eli Zaretskii
2016-07-07 17:38 ` Michael Heerdegen
2016-07-07 17:57 ` Dmitry Antipov
2016-07-07 20:34 ` Michael Heerdegen
2016-07-08 6:14 ` Eli Zaretskii
2016-07-12 21:53 ` Michael Heerdegen
2016-07-13 15:52 ` Michael Heerdegen
2016-07-13 20:19 ` Eli Zaretskii
2016-07-13 21:28 ` Michael Heerdegen
2016-07-13 20:16 ` Eli Zaretskii
2016-07-13 21:23 ` Michael Heerdegen
2016-07-14 14:58 ` Eli Zaretskii
2016-07-14 18:32 ` Michael Heerdegen
2016-07-23 16:16 ` Michael Heerdegen
2016-07-23 16:30 ` Eli Zaretskii
2016-09-12 20:18 ` Michael Heerdegen
2016-09-13 12:25 ` Richard Stallman
2016-09-13 14:40 ` Eli Zaretskii
2016-09-13 15:58 ` Michael Heerdegen
2016-09-14 17:42 ` Eli Zaretskii
2016-07-14 16:15 ` Adrián Medraño Calvo
2016-07-14 18:30 ` Michael Heerdegen
2016-07-14 18:49 ` Eli Zaretskii [this message]
2016-07-14 21:54 ` Michael Heerdegen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83shvc6ond.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23912@debbugs.gnu.org \
--cc=adrian@medranocalvo.com \
--cc=michael_heerdegen@web.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.