From: Paul Eggert <eggert@cs.ucla.edu>
To: emacs-devel@gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>, Steinar Bang <sb@dod.no>
Subject: Re: The emacs_backtrace "feature"
Date: Mon, 24 Sep 2012 10:29:35 -0700 [thread overview]
Message-ID: <5060987F.3020108@cs.ucla.edu> (raw)
In-Reply-To: <8739279zzx.fsf@dod.no>
On 09/24/2012 08:55 AM, Steinar Bang wrote:
> Can you get a backtrace even if the core is from an executable that was
> compiled without debug information?
Yes. Debug info doesn't affect the backtrace.
It's more useful, though, to get a backtrace from an executable
built with debug information, just as it's more useful to get
a core dump that way. One *can* analyze either one without the
debug information, but it's no picnic.
On 09/24/2012 07:27 AM, Lars Ingebrigtsen wrote:
> "let's just spew out reams of nearly meaningless data to the terminal"
It's normally just ten lines, maybe 300 bytes total. It's more than
that (500 lines) only if you build emacs with --enable-checking and then
an assertion fails, under the assumption that people who are debugging
prefer to have more debug info. In practice these numbers worked OK
for my use cases; we can change them as further experience suggests.
next prev parent reply other threads:[~2012-09-24 17:29 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 9:49 The emacs_backtrace "feature" Eli Zaretskii
2012-09-21 9:58 ` Andreas Schwab
2012-09-21 10:17 ` Eli Zaretskii
2012-09-21 12:00 ` Andreas Schwab
2012-09-21 19:29 ` Florian Weimer
2012-09-21 19:45 ` Paul Eggert
2012-09-24 15:52 ` Steinar Bang
2012-09-21 12:24 ` Óscar Fuentes
2012-09-21 16:35 ` Stefan Monnier
2012-09-21 16:49 ` Stephen J. Turnbull
2012-09-21 17:07 ` Tom Tromey
2012-09-21 17:41 ` Andreas Schwab
2012-09-21 19:37 ` Paul Eggert
2012-09-22 12:05 ` Richard Stallman
2012-09-22 13:54 ` Christoph Scholtes
2012-09-22 14:23 ` covici
2012-09-24 15:55 ` Steinar Bang
2012-09-24 17:29 ` Paul Eggert [this message]
2012-09-22 12:41 ` Eli Zaretskii
2012-09-22 19:28 ` Paul Eggert
2012-09-23 13:05 ` Stephen J. Turnbull
2012-09-23 14:19 ` Andreas Schwab
2012-09-23 19:30 ` Stephen J. Turnbull
2012-09-23 21:01 ` Nix
2012-09-24 5:00 ` Stephen J. Turnbull
2012-09-24 9:29 ` Nix
2012-09-24 23:55 ` Stephen J. Turnbull
2012-09-29 19:31 ` Juri Linkov
2012-09-29 20:01 ` Eli Zaretskii
2012-09-29 20:51 ` Paul Eggert
2012-09-29 21:19 ` Eli Zaretskii
2012-09-30 1:30 ` Paul Eggert
2012-09-30 9:44 ` messages-buffer-max-lines (was: The emacs_backtrace "feature") Juri Linkov
2012-10-01 5:51 ` messages-buffer-max-lines Paul Eggert
2012-10-01 6:50 ` messages-buffer-max-lines Chong Yidong
2012-09-30 1:48 ` The emacs_backtrace "feature" Stefan Monnier
2012-09-30 7:14 ` Eli Zaretskii
2012-09-30 7:24 ` Paul Eggert
2012-10-01 2:54 ` Chong Yidong
2012-10-01 11:43 ` Lars Magne Ingebrigtsen
2012-09-21 21:40 ` Richard Stallman
2012-09-22 6:53 ` Stephen J. Turnbull
2012-09-24 14:27 ` 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=5060987F.3020108@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=sb@dod.no \
/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).