From: Eli Zaretskii <eliz@gnu.org>
To: Christian Biesinger <cbiesinger@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] Add Objfile.lookup_{global,static}_symbol functions
Date: Sat, 27 Jul 2019 07:52:00 -0000 [thread overview]
Message-ID: <838ssjnccp.fsf@gnu.org> (raw)
In-Reply-To: <20190727003056.41789-1-cbiesinger@google.com> (gdb-patches@sourceware.org)
> Date: Fri, 26 Jul 2019 19:30:56 -0500
> From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
> Cc: Christian Biesinger <cbiesinger@google.com>
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index cc1d58520d..d8fb4cfe7f 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -36,6 +36,9 @@
> ** gdb.Type has a new property 'objfile' which returns the objfile the
> type was defined in.
>
> + ** gdb.Objfile has new methods 'lookup_global_symbol' and
> + 'lookup_static_symbol' to lookup a symbol from this objfile only.
> +
This part is OK.
> +@defun Objfile.lookup_global_symbol (name @r{[}, domain@r{]})
> +Search for a global symbol named @var{name} in this objfile. Optionally, the
> +search scope can be restricted with the @var{domain} argument.
> +The @var{domain} argument must be a domain constant defined in the @code{gdb}
> +module and described in @ref{Symbols In Python}. This function is similar to
> +@code{gdb.lookup_global_symbol}, except that the search is limited to this
> +objfile.
> +
> +The result is a @code{gdb.Symbol} object or @code{None} if the symbol
> +is not found.
> +@end defun
> +
> +@defun Objfile.lookup_global_symbol (name @r{[}, domain@r{]})
I guess you meant lookup_static_symbol here?
> +Search for a global symbol with static linkage named @var{name} in this
> +objfile. Optionally, the search scope can be restricted with the @var{domain}
> +argument.
> +The @var{domain} argument must be a domain constant defined in the @code{gdb}
> +module and described in @ref{Symbols In Python}. This function is similar to
> +@code{gdb.lookup_global_symbol}, except that the search is limited to this
> +objfile.
> +
> +The result is a @code{gdb.Symbol} object or @code{None} if the symbol
> +is not found.
> +@end defun
As the description of both methods is almost identical, I wonder
whether it wouldn't be better to have the second method be described
as "Like @code{lookup_global_symbol}, but ..." and tell the
differences between them.
Thanks.
next prev parent reply other threads:[~2019-07-27 7:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 22:09 [PATCH] Add an Objfile.lookup_global_symbol function Christian Biesinger via gdb-patches
2019-06-26 15:37 ` Eli Zaretskii
2019-06-26 21:05 ` Tom Tromey
2019-06-27 2:36 ` Eli Zaretskii
2019-06-26 15:38 ` Eli Zaretskii
2019-06-26 21:12 ` Tom Tromey
2019-07-08 21:59 ` Christian Biesinger via gdb-patches
2019-07-09 15:42 ` Eli Zaretskii
2019-07-09 18:44 ` Christian Biesinger via gdb-patches
2019-07-09 19:16 ` Eli Zaretskii
2019-07-22 20:51 ` Christian Biesinger via gdb-patches
2019-07-23 1:30 ` Simon Marchi
2019-07-23 14:47 ` Eli Zaretskii
2019-07-26 1:38 ` Christian Biesinger via gdb-patches
2019-07-26 1:38 ` [PATCH v2] " Christian Biesinger via gdb-patches
2019-07-26 6:19 ` Eli Zaretskii
2019-07-27 0:31 ` [PATCH v3] Add Objfile.lookup_{global,static}_symbol functions Christian Biesinger via gdb-patches
2019-07-27 7:52 ` Eli Zaretskii [this message]
2019-07-27 18:31 ` [PATCH v4] " Christian Biesinger via gdb-patches
2019-07-27 18:38 ` Eli Zaretskii
2019-07-30 1:03 ` Simon Marchi
2019-07-30 1:51 ` [PATCH v5] " Christian Biesinger via gdb-patches
2019-07-30 14:59 ` Eli Zaretskii
2019-07-26 15:40 ` [PATCH] Add an Objfile.lookup_global_symbol function Simon Marchi
2019-07-23 14:54 ` Eli Zaretskii
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=838ssjnccp.fsf@gnu.org \
--to=eliz@gnu.org \
--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