From: Joseph Mingrone <jrm@ftfl.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: 18411@debbugs.gnu.org
Subject: bug#18411: new coredump
Date: Mon, 08 Sep 2014 13:10:09 -0300 [thread overview]
Message-ID: <86r3zm6qla.fsf@gly.ftfl.ca> (raw)
In-Reply-To: <qx61gyun5s.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 08 Sep 2014 11:50:23 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Joseph Mingrone wrote:
>
>> I've included information from a second core dump in case it's helpful.
>> I did run the xbacktrace, but it just reported the same information at
>> the end under "Lisp Backtrace:".
>>
>> In this case I wasn't immediately aware of the coredump, so I'm not
>> sure if it happened with a C-x C-c.
>>
>> http://slexy.org/view/s20zQtacZ9
>
> Also available at http://debbugs.gnu.org/18411#23,
> but the message was too big for the bug-gnu-emacs mailing list.
> Please send large backtraces etc as compressed attachments in future.
Will do. Thanks.
next prev parent reply other threads:[~2014-09-08 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 15:39 bug#18411: 24.3; Emacs (daemon) core dumps after save-buffers-kill-terminal Joseph Mingrone
2014-09-05 16:08 ` bug#18411: No .gbdinit file in src/ directory Joseph Mingrone
2014-09-05 16:18 ` Glenn Morris
2014-09-05 16:47 ` Joseph Mingrone
2014-09-05 17:55 ` Eli Zaretskii
2014-09-08 15:08 ` bug#18411: new coredump Joseph Mingrone
2014-09-08 15:50 ` Glenn Morris
2014-09-08 16:10 ` Joseph Mingrone [this message]
2015-09-13 16:27 ` Joseph Mingrone
2020-09-09 9:52 ` Lars Ingebrigtsen
2020-09-09 12:29 ` Joseph Mingrone
2020-09-09 12:32 ` Lars Ingebrigtsen
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=86r3zm6qla.fsf@gly.ftfl.ca \
--to=jrm@ftfl.ca \
--cc=18411@debbugs.gnu.org \
--cc=rgm@gnu.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).