From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Jon Grant <jg@jguk.org>, gdb@sourceware.org
Subject: Re: gdb backtrace include library as well as symbol name
Date: Mon, 26 Sep 2011 15:36:00 -0000 [thread overview]
Message-ID: <20110926153601.GH27340@adacore.com> (raw)
In-Reply-To: <20110926063307.GA1031@host1.jankratochvil.net>
> > Is there a way to get the "bt" command to output the library or ELF
> > binary file that the symbol orginates in? Would be handy if this
> > could even be the default:
>
> Yes, this is common RFE. It was discussed in the thread:
> Re: [patch] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename)
> http://sourceware.org/ml/gdb-patches/2011-07/msg00796.html
I understood that thread as being something slightly different.
But what's being asked here is that the name of the exe being
debugged be printed for symbols in the main exe. This is the only
time as far as I known when the name of the objfile is not
printed, so I think that the current output is fine.
There has been a project of decorated backtraces, which allows
a user to enhance them via Python. Have you looked at this project?
Not sure if this project made it to the main repository, of if
it is still only in Archer, though.
> > #0 0xb7773424 in __kernel_vsyscall ()
> > #0 Doesn't show lib. I think this is glibc.
>
> It is Linux kernel provided [vdso], it has DWARF info.
To complete what Jan said, it is in memory, but does not have
a corresponding file.
--
Joel
next prev parent reply other threads:[~2011-09-26 15:36 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 [this message]
2011-10-05 18:47 ` Tom Tromey
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=20110926153601.GH27340@adacore.com \
--to=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).