From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: dak@gnu.org, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r116836: Avoid GC crashes.
Date: Mon, 24 Mar 2014 18:48:21 +0200 [thread overview]
Message-ID: <83siq71r1m.fsf@gnu.org> (raw)
In-Reply-To: <532F4B35.9080304@dancol.org>
> Date: Sun, 23 Mar 2014 13:59:33 -0700
> From: Daniel Colascione <dancol@dancol.org>
> CC: dak@gnu.org, schwab@linux-m68k.org, rms@gnu.org, emacs-devel@gnu.org
>
> How about we add code to automatically run gdb and collect a crash dump?
Not sure it would help. A backtrace, even a full one, usually
immediately raises questions that need a live GDB session and an end
user ready to use it, to answer them. Without that, a backtrace is
more often than not just a teaser.
> We can't use MiniDumpWriteDump because gdb can't read Windows minidump
> files, and windbg can't understand DWARF symbols.
Right.
> Or actually, how about integrating Google's Breakpad? It doesn't require
> a local gdb, and it comes with a minidump-2-core utility that supposedly
> lets gdb debug the resulting dump files.
According to this:
https://code.google.com/p/google-breakpad/issues/detail?id=436
it doesn't support GCC-produced DWARF2 debug info, unless you apply
patches both to Breakpad and to Binutils.
next prev parent reply other threads:[~2014-03-24 16:48 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1WR8jg-0006nL-At@vcs.savannah.gnu.org>
2014-03-21 23:41 ` [Emacs-diffs] trunk r116836: Avoid GC crashes Daniel Colascione
2014-03-21 23:59 ` Glenn Morris
2014-03-22 2:35 ` Glenn Morris
2014-03-21 23:59 ` Juanma Barranquero
2014-03-22 1:22 ` Daniel Colascione
2014-03-22 1:29 ` Juanma Barranquero
2014-03-22 1:37 ` Daniel Colascione
2014-03-22 2:30 ` Stefan Monnier
2014-03-22 6:41 ` David Kastrup
2014-03-22 23:56 ` Richard Stallman
2014-03-23 7:12 ` Andreas Schwab
2014-03-23 16:07 ` Eli Zaretskii
2014-03-23 18:54 ` Daniel Colascione
2014-03-23 19:09 ` Eli Zaretskii
2014-03-23 19:53 ` Daniel Colascione
2014-03-23 20:10 ` Eli Zaretskii
2014-03-23 20:36 ` Daniel Colascione
2014-03-23 20:55 ` David Kastrup
2014-03-24 3:45 ` Eli Zaretskii
2014-03-23 20:59 ` Daniel Colascione
2014-03-24 16:48 ` Eli Zaretskii [this message]
2014-03-25 12:42 ` Richard Stallman
2014-03-25 12:49 ` Daniel Colascione
2014-03-25 22:41 ` Richard Stallman
2014-03-25 22:43 ` Daniel Colascione
2014-03-25 15:24 ` Dmitry Antipov
2014-03-25 18:01 ` Eli Zaretskii
2014-03-25 22:40 ` Richard Stallman
2014-03-25 15:43 ` Eli Zaretskii
2014-03-25 22:39 ` Richard Stallman
2014-03-26 3:49 ` Eli Zaretskii
2014-03-26 13:46 ` Richard Stallman
2014-03-26 15:24 ` Eli Zaretskii
2014-03-24 5:50 ` Ivan Andrus
2014-03-24 16:51 ` Eli Zaretskii
2014-03-24 17:12 ` Ivan Andrus
2014-03-22 23:57 ` Richard Stallman
2014-03-23 0:14 ` Daniel Colascione
2014-03-23 3:58 ` Eli Zaretskii
2014-03-23 7:05 ` Andreas Schwab
2014-03-23 16:05 ` Eli Zaretskii
2014-03-23 16:27 ` Andreas Schwab
2014-03-23 14:56 ` Richard Stallman
2014-03-22 23:57 ` Richard Stallman
2014-03-26 14:42 ` Rüdiger Sonderfeld
2014-03-27 17:47 ` Eli Zaretskii
2014-03-28 14:27 ` gNewSense QEMU setup [Was: Re: [Emacs-diffs] trunk r116836: Avoid GC crashes] Dmitry Antipov
2014-03-28 23:17 ` Richard Stallman
2014-03-29 0:00 ` Daniel Colascione
2014-03-30 0:24 ` Richard Stallman
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=83siq71r1m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dak@gnu.org \
--cc=dancol@dancol.org \
--cc=emacs-devel@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).