This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Python Symbol API question/weirdness
- From: Pedro Alves <palves at redhat dot com>
- To: Evan Driscoll <evaned at gmail dot com>, gdb at sourceware dot org
- Date: Tue, 27 Jun 2017 11:56:40 +0100
- Subject: Re: Python Symbol API question/weirdness
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=palves at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 571B0A8324
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 571B0A8324
- References: <CAAR9PsWzg0Xpx4iVhpEMyYTqEMtosXVDPe9sYSYbw9UG=5OFJQ@mail.gmail.com>
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.
Thanks,
Pedro Alves