From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Simon Marchi <simark@simark.ca>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb/python: Introduce gdb.lookup_all_static_symbols
Date: Mon, 21 Oct 2019 22:37:00 -0000 [thread overview]
Message-ID: <CAPTJ0XEAtJRp=zCLWzvtMidZSXNnDkdy-OxafHeNSA3SuOVQ5w@mail.gmail.com> (raw)
In-Reply-To: <32eba92d-55a9-5694-cec5-80001d8ff1ae@simark.ca>
On Tue, Oct 15, 2019 at 2:28 PM Simon Marchi <simark@simark.ca> wrote:
>
> On 2019-10-15 12:46 p.m., Andrew Burgess wrote:
> > If gdb.lookup_static_symbol is going to return a single symbol then it
> > makes sense (I think) for it to return a context sensitive choice of
> > symbol, that is the static symbol that would be visible to the program
> > at that point.
>
> I remember discussing this with Christian, and I didn't have a strong option. But
> now, I tend to agree with Andrew.
>
> I see two use cases here:
>
> 1. I want to get all static symbols named `foo`. In which case, I'd use the
> function Andrew proposes in this patch.
> 2. I want to get the static symbol named `foo` that's visible from a certain
> point, perhaps a given block or where my program is currently stopped at.
> Ideally, we would have a "CompilationUnit" object type in Python, such that
> I could use
>
> block.compunit.lookup_static_symbol('foo')
>
> or
>
> gdb.current_compunit().lookup_static_symbol('foo')
So technically, those don't give you "the static symbol named `foo`
that's visible from [this] point", because there could be static
variable in the function.
Since we already have block objects, should this new function
optionally take a block to start the lookup in?
Either way, I'm happy with this patch; I've come around to y'all's view.
Christian
next prev parent reply other threads:[~2019-10-21 22:37 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 [this message]
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
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='CAPTJ0XEAtJRp=zCLWzvtMidZSXNnDkdy-OxafHeNSA3SuOVQ5w@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).