From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Use add_setshow_zuinteger_unlimited_cmd in remote.c
Date: Mon, 09 Jul 2018 15:11:00 -0000 [thread overview]
Message-ID: <dbc29ff9-6dfa-e75c-2212-52c7fbe44b4b@redhat.com> (raw)
In-Reply-To: <20180702221146.20201-1-andrew.burgess@embecosm.com>
Hi Andrew,
Noticed a typo below.
On 07/02/2018 11:11 PM, Andrew Burgess wrote:
> @@ -21161,16 +21161,24 @@
> @anchor{set remote hardware-breakpoint-limit}
> @item set remote hardware-watchpoint-limit @var{limit}
> @itemx set remote hardware-breakpoint-limit @var{limit}
> -Restrict @value{GDBN} to using @var{limit} remote hardware breakpoint or
> -watchpoints. A limit of -1, the default, is treated as unlimited.
> +Restrict @value{GDBN} to using @var{limit} remote hardware watchpoints
> +or breakpoints. The @var{limit} can be set to 0 to disable hardware
> +watchpoints or breakpoints, and @code{unilmited} for unlimited
> +watchpoints or breakpoints.
Typo:
"unilmited" -> unlimited
> Set the maximum length (in bytes) of a target hardware watchpoint."), _("\
> Show the maximum length (in bytes) of a target hardware watchpoint."), _("\
> -Specify a negative limit for unlimited."),
> - NULL, NULL, /* FIXME: i18n: The maximum
> - length (in bytes) of a target
> - hardware watchpoint is %s. */
> +Specify \"unlimited\" to allow unlimited sized watchpoints."),
While at it, a nit, shouldn't "unlimited sized" be hyphenated,
being a compound adjective:
unlimited-sized watchpoints.
(in contrast with allowing an unlimited number of
"sized watchpoints", whatever that would be.)
Maybe this would be clearest:
Specify \"unlimited\" to allow watchpoints of unlimited size."
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-07-09 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 22:11 Andrew Burgess
2018-07-04 16:46 ` Eli Zaretskii
2018-07-07 2:01 ` Simon Marchi
2018-07-09 15:11 ` Pedro Alves [this message]
2018-07-09 17:10 ` 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=dbc29ff9-6dfa-e75c-2212-52c7fbe44b4b@redhat.com \
--to=palves@redhat.com \
--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