From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Jon Grant <jg@jguk.org>,
gdb@sourceware.org
Subject: Re: gdb backtrace include library as well as symbol name
Date: Wed, 05 Oct 2011 18:47:00 -0000 [thread overview]
Message-ID: <m31uurjmxe.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110926153601.GH27340@adacore.com> (Joel Brobecker's message of "Mon, 26 Sep 2011 08:36:01 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Jan> Yes, this is common RFE. It was discussed in the thread:
Jan> Re: [patch] GDB 7.2: new feature for "backtrace" that cuts
Jan> path to file (remain filename)
Jan> http://sourceware.org/ml/gdb-patches/2011-07/msg00796.html
Joel> I understood that thread as being something slightly different.
Joel> But what's being asked here is that the name of the exe being
Joel> debugged be printed for symbols in the main exe. This is the only
Joel> time as far as I known when the name of the objfile is not
Joel> printed, so I think that the current output is fine.
I think it would be a decent addition.
What happened to the patch which Jan references? It also seemed like a
good idea, or at least a good one once minor changes were made.
Joel> There has been a project of decorated backtraces, which allows
Joel> a user to enhance them via Python. Have you looked at this project?
Joel> Not sure if this project made it to the main repository, of if
Joel> it is still only in Archer, though.
Phil is reimplementing this in a better way.
Tom
prev parent reply other threads:[~2011-10-05 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 22:30 Jon Grant
2011-09-26 6:33 ` Jan Kratochvil
2011-09-26 15:36 ` Joel Brobecker
2011-10-05 18:47 ` Tom Tromey [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m31uurjmxe.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=jg@jguk.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.
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).