From: "Andrew Burgess" <aburgess@broadcom.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Extra error message from update_watchpoint
Date: Wed, 30 Oct 2013 17:13:00 -0000 [thread overview]
Message-ID: <52713E2F.2030709@broadcom.com> (raw)
In-Reply-To: <83a9hqepgt.fsf@gnu.org>
On 30/10/2013 3:41 PM, Eli Zaretskii wrote:
>> Date: Wed, 30 Oct 2013 11:49:18 +0000
>> From: "Andrew Burgess" <aburgess@broadcom.com>
>> cc: gdb-patches@sourceware.org
>>
>> OK, here are a few alternatives, feel free to pick your favourites:
>>
>> (1) The original:
>> error (_("Software read/access watchpoints not supported."));
>>
>> (2) Pedro's original replacement:
>> error (_("Hardware watchpoint support disabled. "
>> "See set/show can-use-hw-watchpoints."));
>>
>> (3) The original + why we can't use H/W watchpoints (bit long):
>> error (_("Software read/access watchpoints not supported, "
>> "re-enable hardware watchpoints using "
>> "\"set can-use-hw-watchpoints 1\""));
>>
>> (4) Same, but with a newline to keep it under 80 chars, not sure if
>> multi-line errors are acceptable though.
>> error (_("Software read/access watchpoints not supported.\n"
>> "Enable hardware watchpoints using "
>> "\"set can-use-hw-watchpoints 1\""));
>>
>> (5) Mention that H/W watchpoints are disabled, but not how to re-enable
>> them, though given the user has done the disabling this might be enough
>> to prompt them. This is single line, and just under 80 chars.
>> error (_("Software read/access watchpoints not supported, "
>> "hardware watchpoints disabled."));
>>
>>
>> My favourite is (5) at the moment, but I'll take whatever makes everyone
>> else happy :)
>
> None of the above really explains to the user why GDB is going to
> refuse to abide by her command.
>
> A good message should say something like "Cannot do SOMETHING because
> SOME-REASON."
>
> But I don't want to be in the position of blocking a commit due to
> something that is just MO, so feel free to ignore me.
I'd rather make you happy if possible, never hurts to suck up right ;-)
The following follows the structure you gave, I'd be happy to go with
this except that it's longer than 80 character... is that an issue?
"Can't set read/access watchpoint, software read/access watchpoints not
supported, and hardware watchpoints disabled (see set/show
can-use-hw-watchpoints)."
Thanks,
Andrew
next prev parent reply other threads:[~2013-10-30 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 9:20 Andrew Burgess
2013-10-18 17:18 ` Pedro Alves
2013-10-29 16:44 ` Andrew Burgess
2013-10-29 17:09 ` Pedro Alves
2013-10-29 17:19 ` Eli Zaretskii
2013-10-29 17:38 ` Andrew Burgess
2013-10-29 17:52 ` Pedro Alves
2013-10-29 19:09 ` Eli Zaretskii
2013-10-30 11:49 ` Andrew Burgess
2013-10-30 15:41 ` Eli Zaretskii
2013-10-30 17:13 ` Andrew Burgess [this message]
2013-10-30 18:41 ` Eli Zaretskii
2013-10-31 13:05 ` Andrew Burgess
2013-10-30 18:48 ` Pedro Alves
2013-10-30 19:19 ` 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=52713E2F.2030709@broadcom.com \
--to=aburgess@broadcom.com \
--cc=eliz@gnu.org \
--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