From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: jwiegley@gmail.com, 22058@debbugs.gnu.org
Subject: bug#22058: 25.1.50; emacs_backtrace.txt
Date: Mon, 30 Nov 2015 08:22:44 -0800 (PST) [thread overview]
Message-ID: <2273d74b-f30c-4c39-97b5-6e10ecff581f@default> (raw)
In-Reply-To: <<83k2ozmq6m.fsf@gnu.org>>
> > > Such a stack trace offers nothing actionable.
> >
> > Is there a simple way for me to recognize that, from the
> > backtrace?
>
> A good rule of thumb is: if the backtrace includes this pair of lines:
>
> > Exception 0xc0000005 at this address:
> > 774374f6
>
> and if the address starts with 7, then we will not be able to convert
> it to any meaningful address in the Emacs application code. (The
> exception code does not need to be 0xc0000005, although it usually
> is.)
Excellent. Wish I'd have known that long ago. How about mentioning
this in (emacs) `Crashing'?
Or perhaps the code that creates the emacs_backtrace.txt file could
just print a message in such a case, saying that no useful backtrace
file could be created?
next parent reply other threads:[~2015-11-30 16:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<f774949d-8945-4c73-a5e8-ed26c511c3bf@default>
[not found] ` <<m2d1ur36r0.fsf@newartisans.com>
[not found] ` <<929593b8-ad63-4b4a-9587-1eef6e821cc6@default>
[not found] ` <<83k2ozmq6m.fsf@gnu.org>
2015-11-30 16:22 ` Drew Adams [this message]
2015-11-30 17:48 ` bug#22058: 25.1.50; emacs_backtrace.txt Eli Zaretskii
[not found] ` <<m2wpszuwtw.fsf@newartisans.com>
[not found] ` <<CAAeL0SRkN+PJF+Kn6DPi0mYcx_HnFNdLnY6fgGjSbX30d1sxEg@mail.gmail.com>
[not found] ` <<m2lh9esxns.fsf@newartisans.com>
[not found] ` <<3505c131-e8ab-4f86-8828-b378bc9dac47@default>
[not found] ` <<222e11d1-95f0-4ade-8f86-18f034eabb1e@default>
[not found] ` <<83h9k2kwsa.fsf@gnu.org>
2015-12-01 16:11 ` Drew Adams
2015-12-01 16:22 ` Eli Zaretskii
[not found] ` <<32860321-e9f0-4057-9e4a-b2be4aa5dc82@default>
[not found] ` <<8337vmkul2.fsf@gnu.org>
2015-12-01 16:56 ` Drew Adams
2015-12-01 18:45 ` Eli Zaretskii
2015-11-29 23:37 Drew Adams
2015-11-30 14:24 ` John Wiegley
2015-11-30 15:10 ` Drew Adams
2015-11-30 16:01 ` Eli Zaretskii
2015-11-30 19:11 ` John Wiegley
2015-11-30 19:31 ` Drew Adams
2015-11-30 21:13 ` Juanma Barranquero
2015-12-01 2:36 ` John Wiegley
2015-12-01 3:51 ` Drew Adams
2015-12-01 6:17 ` Drew Adams
2015-12-01 15:34 ` Eli Zaretskii
2015-12-01 15:26 ` 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=2273d74b-f30c-4c39-97b5-6e10ecff581f@default \
--to=drew.adams@oracle.com \
--cc=22058@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jwiegley@gmail.com \
/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).