Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Roman Popov <ripopov@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb@sourceware.org
Subject: Re: Python API: Getting symbol by address
Date: Thu, 21 Dec 2017 22:56:00 -0000	[thread overview]
Message-ID: <CAATAM3EhPrrSXi6OcfesE=nNW9gfQmq_wbyXRGU+Syo+sn61WQ@mail.gmail.com> (raw)
In-Reply-To: <cbab93222dec1eb79473740651a00baf@polymtl.ca>

Thanks, so it is just not implemented yet.
Unfortunately I can't quickly write a patch myself because I'm not familiar
with gdb codebase. I don't even know how debuggers work to be honest .

I've noticed that GDB can pretty-print function/method pointer values like
this:

print ( some_func_ptr_gdbvalue )
>>> (void (*)(int, int)) 0x4049f7 <test(int, int)>

So I've unblocked myself by this ugly text parsing workaround:

s = str (some_func_ptr_gdbvalue)
symbol_name = s[s.find("<") + 1 : s.rfind(">")]
gdb_symbol = gdb.lookup_symbol(symbol_name)


2017-12-21 14:24 GMT-08:00 Simon Marchi <simon.marchi@polymtl.ca>:

> On 2017-12-21 13:20, Roman Popov wrote:
>
>> Hello,
>> I have collection in C++ that stores pointers to functions and methods. I
>> want to pretty-print pointed method and functions names.
>>
>> It is possible using GDB shell, for example:
>>
>> (gdb) info symbol 0x405ece
>>
>> top::test_thread() in section .text of test_procs
>>
>>
>> However I found no way to do the same using Python API.  Why such
>> limitation?
>>
>> P/S Same question on stackoverflow :
>> https://stackoverflow.com/questions/47916564/gdb-python-api-
>> getting-symbol-name-from-address
>>
>> Thanks,
>> Roman
>>
>
> Hi Roman,
>
> As most things in the Python API (and GDB in general), it's likely because
> no one took the time to do it.  I don't see any technical reason not to
> have it.  If you take a shot at writing a patch for this, feel free to ask
> if you are blocked.
>
> Thanks,
>
> Simon
>


      reply	other threads:[~2017-12-21 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 18:20 Roman Popov
2017-12-21 22:24 ` Simon Marchi
2017-12-21 22:56   ` Roman Popov [this message]

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='CAATAM3EhPrrSXi6OcfesE=nNW9gfQmq_wbyXRGU+Syo+sn61WQ@mail.gmail.com' \
    --to=ripopov@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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