From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/5] gdb/python: Add gdb.Architecture.registers method
Date: Wed, 17 Jun 2020 21:25:54 +0300 [thread overview]
Message-ID: <83zh91zgzx.fsf@gnu.org> (raw)
In-Reply-To: <c2e767bc38f3513c684bda352949e04b76909988.1592415321.git.andrew.burgess@embecosm.com> (message from Andrew Burgess on Wed, 17 Jun 2020 18:38:07 +0100)
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Wed, 17 Jun 2020 18:38:07 +0100
> gdb/ChangeLog:
>
> * Makefile.in (SUBDIR_PYTHON_SRCS): Add py-registers.c
> * python/py-arch.c (archpy_registers): New function.
> (arch_object_methods): Add 'registers' method.
> * python/py-registers.c: New file.
> * python/python-internal.h
> (gdbpy_new_register_descriptor_iterator): Declare.
> (gdbpy_initialize_registers): Declare.
> * python/python.c (do_start_initialization): Call
> gdbpy_initialize_registers.
> * NEWS: Mention additions to the Python API.
>
> gdb/testsuite/ChangeLog:
>
> * gdb.python/py-arch-reg-names.exp: New file.
>
> gdb/doc/ChangeLog:
>
> * python.texi (Python API): Add new section the menu.
^^^^^^^^
"to the menu".
> (Frames In Python): Add new @anchor.
> (Architectures In Python): Document new registers method.
> (Registers In Python): New section.
The documentation parts are approved, with a few nits:
> +@anchor{gdbpy_architecture_registers}
> +@defun Architecture.registers (@r{[} @var{reggroup} @r{]})
> +Return a @code{gdb.RegisterDescriptorIterator} (@pxref{Registers In
> +Python}) for all of the registers in @var{reggroup}, a string that is
> +the name of a register group. If @var{reggroup} is missing, or is the
^^^^^^^
"omitted" is better here.
> +empty string, then the register group @dfn{all} is assumed.
^^^^^^^^^
Please use @samp here instead of @dfn. The latter is for markup of
terminology, which is not what you want here.
> +A @code{gdb.RegisterDescriptor} does not provide the value of a
> +register (@pxref{gdbpy_frame_read_register,,@code{Frame.read_register}} for reading a registers
^^^^^^^^^
You meant "register's" here, with the apostrophe, right?
Thanks.
next prev parent reply other threads:[~2020-06-17 18:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 17:38 [PATCH 0/5] Python Unwinders and Inline Frames Andrew Burgess
2020-06-17 17:38 ` [PATCH 1/5] gdb: Remove deprecated_set_gdbarch_data Andrew Burgess
2020-06-18 21:11 ` Tom Tromey
2020-06-17 17:38 ` [PATCH 2/5] gdb/python: Add architecture method to gdb.PendingFrame Andrew Burgess
2020-06-17 18:20 ` Eli Zaretskii
2020-06-18 21:18 ` Tom Tromey
2020-06-17 17:38 ` [PATCH 3/5] gdb/python: Add gdb.Architecture.registers method Andrew Burgess
2020-06-17 18:25 ` Eli Zaretskii [this message]
2020-06-18 21:24 ` Tom Tromey
2020-06-17 17:38 ` [PATCH 4/5] gdb/python: New method to access list of register groups Andrew Burgess
2020-06-17 18:27 ` Eli Zaretskii
2020-06-17 18:40 ` Christian Biesinger
2020-06-18 8:44 ` Andrew Burgess
2020-06-18 21:27 ` Tom Tromey
2020-06-17 17:38 ` [PATCH 5/5] gdb: Fix Python unwinders and inline frames Andrew Burgess
2020-06-17 21:14 ` Luis Machado
2020-06-18 8:25 ` Andrew Burgess
2020-06-18 10:29 ` Luis Machado
2020-06-18 17:42 ` Andrew Burgess
2020-06-18 21:35 ` Tom Tromey
2020-06-22 15:47 ` Andrew Burgess
2020-06-23 14:16 ` Luis Machado
2020-07-02 21:07 ` Andrew Burgess
2020-07-06 17:43 ` Andrew Burgess
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=83zh91zgzx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.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