From: buddhika chamith <chamibuddhika@gmail.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: Libdw sample for reading function names and addresses
Date: Mon, 10 Nov 2014 23:41:52 -0500 [thread overview]
Message-ID: <CAPO7Hz80uN19mZE9ogsVnDuz9Fv1ydpmzaX9gP-mkjXivq6=sw@mail.gmail.com> (raw)
In-Reply-To: m2y4rjakct.fsf@redhat.com
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
Thanks for the replies. I will have a look. Will get back if I get further
issues.
Regards
Bud
On Sun, Nov 9, 2014 at 8:57 PM, Petr Machata <pmachata@redhat.com> wrote:
> Mark Wielaard <mjw@redhat.com> writes:
>
> > On Sat, 2014-11-08 at 22:00 -0500, buddhika chamith wrote:
> >> I have a requirement to read off function names and addresses from an
> >> ELF binary debug symbols. Is there any such piece of code that's
> >> already there that you have written? I had a look at some elfutils
> >> codes (e.g: nm.c) in the hope of adapting them to my requirement. But
> >> the libdw API is seems bit intimidating to me given that I have
> >> little knowledge on Dwarf format.
> >
> > There is no such thing as "debug symbols". There are various DIEs (Debug
> > Information Entries) that can be associated with particular address
> > ranges though. You might want to read a bit about DWARF at
> > http://dwarfstd.org/
>
> There's also .symtab, if that's enough. dwfl_module_getsymtab and
> dwfl_module_getsym should be able to retrieve it even from a separate
> debug-info file, in case it was stripped, otherwise gelf_getsym would be
> enough (and easier to set up than Dwfl).
>
> Petr.
>
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 1823 bytes --]
next reply other threads:[~2014-11-11 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 4:41 buddhika chamith [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-10 1:57 Petr Machata
2014-11-09 17:04 Mark Wielaard
2014-11-09 3:00 buddhika chamith
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='CAPO7Hz80uN19mZE9ogsVnDuz9Fv1ydpmzaX9gP-mkjXivq6=sw@mail.gmail.com' \
--to=chamibuddhika@gmail.com \
--cc=elfutils-devel@lists.fedorahosted.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).