From: Daniel Jacobowitz <drow@false.org>
To: Bruce Korb <bruce.korb@gmail.com>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>,
gdb@sourceware.org, gdb@gnu.org
Subject: Re: How does one get static procedure names?
Date: Tue, 27 Oct 2009 19:43:00 -0000 [thread overview]
Message-ID: <20091027193731.GA16615@caradoc.them.org> (raw)
In-Reply-To: <668c430c0910271233m35b959bepb91df230b6c05ced@mail.gmail.com>
On Tue, Oct 27, 2009 at 12:33:39PM -0700, Bruce Korb wrote:
> Exactly. I know it'd be some work. I think I need to
> call: dlopen(NULL, RTLD_NOW)
No. You need to open the file and have your own ELF and symbol table
reader. They are not in the area mapped by dlopen.
> and then copy & fiddle code out of GDB. yes? :)
GDB is almost certainly not where you want to get this code from. We
just use BFD...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-10-27 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 18:36 Bruce Korb
2009-10-27 18:56 ` Paul Pluzhnikov
2009-10-27 19:11 ` Bruce Korb
2009-10-27 19:31 ` Daniel Jacobowitz
2009-10-27 19:37 ` Bruce Korb
2009-10-27 19:43 ` Daniel Jacobowitz [this message]
2009-10-27 20:03 ` Bruce Korb
2009-10-27 20:10 ` Andreas Schwab
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=20091027193731.GA16615@caradoc.them.org \
--to=drow@false.org \
--cc=bruce.korb@gmail.com \
--cc=gdb@gnu.org \
--cc=gdb@sourceware.org \
--cc=ppluzhnikov@google.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox