From: Matt Rice <ratmice@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Evan Driscoll <evaned@gmail.com>, GDB <gdb@sourceware.org>
Subject: Re: Python Symbol API question/weirdness
Date: Tue, 27 Jun 2017 11:17:00 -0000 [thread overview]
Message-ID: <CACTLOFokU=gBrvCM5DMvYzatpjOUkh6PWQkEGthDFAohs_P7ww@mail.gmail.com> (raw)
In-Reply-To: <570ff52f-214b-98a4-dcc0-74d134c67c3d@redhat.com>
On Tue, Jun 27, 2017 at 3:56 AM, Pedro Alves <palves@redhat.com> wrote:
> On 06/16/2017 09:55 PM, Evan Driscoll wrote:
>
>> Does anyone have any idea what might be going on? I think I don't
>> actually need this to work, but I am curious what is going on. Maybe
>> something with symbol aliases?
>
> I think that you're seeing this because the Python API is only aware
> of debug info symbols, while "raise" etc. above in your examples
> are minimal symbols (i.e., elf symbols), as hinted by:
>
> $2 = (<text variable, no debug info> *) 0x7ffff7a433f0 <__GI_raise>
> ^^^^^^^^^^^^^
>
> Sounds like exposing minsyms to the Python layer would be useful.
> I'm actually surprised it doesn't already expose them somehow.
I think you can get some information about minsyms from decode_line
(gdb) py print(gdb.parse_and_eval("main"))
{<text variable, no debug info>} 0x4004f0 <main>
(gdb) py print('%02x' % gdb.decode_line("main")[1][0].pc)
4004f0
prev parent reply other threads:[~2017-06-27 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 20:55 Evan Driscoll
2017-06-27 10:56 ` Pedro Alves
2017-06-27 11:17 ` Matt Rice [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='CACTLOFokU=gBrvCM5DMvYzatpjOUkh6PWQkEGthDFAohs_P7ww@mail.gmail.com' \
--to=ratmice@gmail.com \
--cc=evaned@gmail.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.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