From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, cbiesinger@google.com
Subject: Re: [PATCH] gdb/python: Introduce gdb.lookup_all_static_symbols
Date: Tue, 15 Oct 2019 17:07:00 -0000 [thread overview]
Message-ID: <83pniyey3m.fsf@gnu.org> (raw)
In-Reply-To: <20191015164647.1837-1-andrew.burgess@embecosm.com> (message from Andrew Burgess on Tue, 15 Oct 2019 17:46:47 +0100)
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: Christian Biesinger <cbiesinger@google.com>, Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Tue, 15 Oct 2019 17:46:47 +0100
>
> gdb/ChangeLog:
>
> * python/py-symbol.c (gdbpy_lookup_all_static_symbols): New
> function.
> * python/python-internal.h (gdbpy_lookup_all_static_symbols):
> Declare new function.
> * python/python.c (python_GdbMethods): Add
> gdb.lookup_all_static_symbols method.
>
> gdb/testsuite/ChangeLog:
>
> * gdb.python/py-symbol.exp: Add test for
> gdb.lookup_all_static_symbols.
>
> gdb/doc/ChangeLog:
>
> * python.texi (Symbols In Python): Add documentation for
> gdb.lookup_all_static_symbols.
The python.texi part is OK, but I think this change also needs a NEWS
entry.
Thanks.
next prev parent reply other threads:[~2019-10-15 17:07 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 [this message]
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
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=83pniyey3m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
/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