From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <aburgess@broadcom.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Extra error message from update_watchpoint
Date: Tue, 29 Oct 2013 17:52:00 -0000 [thread overview]
Message-ID: <526FF5EE.2070509@redhat.com> (raw)
In-Reply-To: <526FF27B.8090209@broadcom.com>
On 10/29/2013 05:38 PM, Andrew Burgess wrote:
> On 29/10/2013 5:19 PM, Eli Zaretskii wrote:
>>> Date: Tue, 29 Oct 2013 16:44:25 +0000
>>> From: "Andrew Burgess" <aburgess@broadcom.com>
>>> cc: "Pedro Alves" <palves@redhat.com>
>>>
>>> diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
>>> index 608463d..68b348d 100644
>>> --- a/gdb/breakpoint.c
>>> +++ b/gdb/breakpoint.c
>>> @@ -1805,7 +1805,8 @@ update_watchpoint (struct watchpoint *b, int reparse)
>>> if (b->base.ops->works_in_software_mode (&b->base))
>>> b->base.type = bp_watchpoint;
>>> else
>>> - error (_("Software read/access watchpoints not supported."));
>>> + error (_("Hardware watchpoint support disabled. "
>>> + "See set/show can-use-hw-watchpoints."));
>>
>> Sorry for chiming in late, but IMO this change is a step backwards:
>> the new warning is much more puzzling than the old one. The old one
>> at least told what was the problem, the new one looks like entirely
>> unrelated (unless you are privy to GDB internals).
>>
>> How about something like
>>
>> Cannot set read/access watchpoints without hardware watchpoint support.
>
>
> If Pedro is happy then I too am happy,
;-) I'm happy. Eli, it wasn't clear to me from your
suggestion -- do you think the "See set/show can-use-hw-watchpoints."
part should or shouldn't be there? (the case here isn't that the
target doesn't support these watchpoint types, but that support
has been manually disabled)
> my original issue was for the case where turning H/W watchpoints
> off resulted in the error:
> Expression cannot be implemented with read/access watchpoint.
>
> which confused me. Anything that's been suggested so far is better than
> the original behaviour :)
--
Pedro Alves
next prev parent reply other threads:[~2013-10-29 17:52 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 [this message]
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
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=526FF5EE.2070509@redhat.com \
--to=palves@redhat.com \
--cc=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