Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bruce Korb <bruce.korb@gmail.com>
To: Bruce Korb <bruce.korb@gmail.com>,
	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 20:03:00 -0000	[thread overview]
Message-ID: <668c430c0910271243l194e6022va045362c830c9662@mail.gmail.com> (raw)
In-Reply-To: <20091027193731.GA16615@caradoc.them.org>

On Tue, Oct 27, 2009 at 12:37 PM, Daniel Jacobowitz <drow@false.org> wrote:
> 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.

OK.  Still not terribly hard:

    {
        static char const exe_fmt[] =
            "/proc/%d/exe";
        char bf[sizeof (exe_fmt) + 12];
        sprintf(bf, exe_fmt, getpid());
        path_len = readlink(bf, exe_path, sizeof (exe_path) - 1);
    }

(This is for Linux only...)

> GDB is almost certainly not where you want to get this code from.  We
> just use BFD...

Ah!  There we go.  That's what I was looking for.  Thank you!


  reply	other threads:[~2009-10-27 19:43 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
2009-10-27 20:03           ` Bruce Korb [this message]
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=668c430c0910271243l194e6022va045362c830c9662@mail.gmail.com \
    --to=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