From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Simon Marchi <simark@simark.ca>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb/python: Introduce gdb.lookup_all_static_symbols
Date: Mon, 11 Nov 2019 16:31:00 -0000 [thread overview]
Message-ID: <CAPTJ0XHHSnPpykwE8e1n_eS5t-z0SOkQ5D3hAZNJV7Dt+2u_=Q@mail.gmail.com> (raw)
In-Reply-To: <20191111162730.GJ11037@embecosm.com>
On Mon, Nov 11, 2019 at 8:27 AM Andrew Burgess
<andrew.burgess@embecosm.com> wrote:
> > Thanks! By the way, should Objfile also get a lookup_static_symbols
> > method now, similar to Objfile.lookup_static_symbol?
> >
> > (I don't personally have a use-case for this, but figured I should
> > ask)
>
> I don't think that's a crazy idea, but I don't plan to write one right
> now.
>
> My interest in this area started when I was auditing how the GDB
> function lookup_static_function (the one in symtab.c) was used, and I
> felt that the way it was used in the python code wasn't quite right.
> I don't have any specific use cases to address.
>
> We can always add extra API methods later if/when there's a need for
> them without breaking backward compatibility, so I'm happy to leave
> this for now.
OK, sounds good.
Christian
next prev parent reply other threads:[~2019-11-11 16:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 16:46 [PATCH] gdb/python: smarter symbol lookup for gdb.lookup_static_symbol Andrew Burgess
2019-09-23 17:18 ` Eli Zaretskii
2019-10-08 11:07 ` [PATCHv2] " Andrew Burgess
2019-10-08 12:01 ` Eli Zaretskii
2019-10-08 16:01 ` Christian Biesinger via gdb-patches
2019-10-15 14:15 ` Andrew Burgess
2019-10-15 16:46 ` [PATCH] gdb/python: Introduce gdb.lookup_all_static_symbols Andrew Burgess
2019-10-15 17:07 ` Eli Zaretskii
2019-10-23 19:15 ` Andrew Burgess
2019-10-24 2:31 ` Eli Zaretskii
2019-10-15 19:28 ` Simon Marchi
2019-10-15 23:32 ` Andrew Burgess
2019-10-21 22:37 ` Christian Biesinger via gdb-patches
2019-10-23 19:14 ` Andrew Burgess
2019-10-24 3:11 ` Simon Marchi
2019-10-24 16:53 ` Andrew Burgess
2019-10-28 5:08 ` Christian Biesinger via gdb-patches
2019-11-01 11:53 ` Andrew Burgess
2019-11-01 13:55 ` Simon Marchi
2019-11-04 17:12 ` Andrew Burgess
2019-11-04 18:28 ` Simon Marchi
2019-11-09 6:23 ` Christian Biesinger via gdb-patches
2019-11-10 22:27 ` Andrew Burgess
2019-11-10 22:37 ` Christian Biesinger via gdb-patches
2019-11-11 16:27 ` Andrew Burgess
2019-11-11 16:31 ` Christian Biesinger via gdb-patches [this message]
2019-10-16 21:53 ` [PATCHv2] gdb/python: smarter symbol lookup for gdb.lookup_static_symbol Christian Biesinger via gdb-patches
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='CAPTJ0XHHSnPpykwE8e1n_eS5t-z0SOkQ5D3hAZNJV7Dt+2u_=Q@mail.gmail.com' \
--to=gdb-patches@sourceware.org \
--cc=andrew.burgess@embecosm.com \
--cc=cbiesinger@google.com \
--cc=simark@simark.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