From: Glenn Morris <rgm@gnu.org>
To: 15062@debbugs.gnu.org
Subject: bug#15062: 24.3.50; emacs_backtrace.txt
Date: Fri, 09 Aug 2013 14:15:35 -0400 [thread overview]
Message-ID: <2lpptmd92w.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83y58arbm9.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 09 Aug 2013 20:57:02 +0300")
>> What would take to pesuade you to run emacs under GDB for a while?
There are 30+ of these "here's a backtrace" reports now.
It seems massively unproductive to keeping trying to solve these issues
without gdb.
prev parent reply other threads:[~2013-08-09 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 15:51 bug#15062: 24.3.50; emacs_backtrace.txt Drew Adams
2013-08-09 16:09 ` Juanma Barranquero
2013-08-09 17:57 ` Eli Zaretskii
2013-08-09 18:15 ` Glenn Morris [this message]
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=2lpptmd92w.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=15062@debbugs.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).