Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bruce Korb <bruce.korb@gmail.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb@sourceware.org, gdb@gnu.org
Subject: Re: How does one get static procedure names?
Date: Tue, 27 Oct 2009 19:11:00 -0000	[thread overview]
Message-ID: <668c430c0910271156m29e5770dyec6de9afa84f01f7@mail.gmail.com> (raw)
In-Reply-To: <8ac60eac0910271140n54923a92u74bd2a909ed05696@mail.gmail.com>

On Tue, Oct 27, 2009 at 11:40 AM, Paul Pluzhnikov
<ppluzhnikov@google.com> wrote:
> On Tue, Oct 27, 2009 at 11:32 AM, Bruce Korb <bruce.korb@gmail.com> wrote:
>
>> I know GDB has some way to do it, but I couldn't locate
>> the code that does it.  A pointer on where to look would
>> be really helpful and greatly appreciated!
>
> Your question is rather unclear :-(

Sorry.   When you do a "bt" using gdb, you see the function
names, whether they be "static" or have global (external)
linkage.  The function backtrace_symbols(), on the other
hand, doe *not* print static scope function names.  Even if
it takes some work, I'd like to "fix" the constraint.  However,
I wasn't able to decipher the gdb source well enough to figure
out how it accomplished this feat.  So, is there some place
in the GDB source where I ought to be looking?

Thank you!

Regards, Bruce


  reply	other threads:[~2009-10-27 18:56 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 [this message]
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
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=668c430c0910271156m29e5770dyec6de9afa84f01f7@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