From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [testsuite] Probe awatch/rwatch support
Date: Fri, 17 Apr 2015 09:34:00 -0000 [thread overview]
Message-ID: <86oamnrtdi.fsf@gmail.com> (raw)
In-Reply-To: <552D2BC6.5060109@redhat.com> (Pedro Alves's message of "Tue, 14 Apr 2015 16:01:26 +0100")
Pedro Alves <palves@redhat.com> writes:
Hi Pedro,
Your patch fixes some fails, but following piece causes a regression
> diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
> index 96d2a14..aa7bc02 100644
> --- a/gdb/breakpoint.c
> +++ b/gdb/breakpoint.c
> @@ -2104,6 +2104,10 @@ update_watchpoint (struct watchpoint *b, int reparse)
> if (!can_use_hw_watchpoints)
> error (_("Can't set read/access watchpoint when "
> "hardware watchpoints are disabled."));
> + else if (target_can_use_hardware_watchpoint (b->base.type, 1, 0)
> + == 0)
> + error (_("Target does not support this type of "
> + "hardware watchpoint."));
> else
> error (_("Expression cannot be implemented with "
> "read/access watchpoint."));
rwatch $pc^M
Target does not support this type of hardware watchpoint.^M
(gdb) FAIL: gdb.base/watchpoint.exp: rwatch disallowed for register based expression
without your patch, it is:
rwatch $pc^M
Expression cannot be implemented with read/access watchpoint.^M
(gdb) PASS: gdb.base/watchpoint.exp: rwatch disallowed for register based expression
I've already had a fix to the regression, that is, return more
information from can_use_hardware_watchpoint, so that the caller
(update_watchpoint) can emit sensible errors accordingly. The patch
looks ugly, so still need some time to improve it. In the meantime,
other bits of your patch is still very useful, and fixes some fails
without any regressions. I'll post them out first.
--
Yao (齐尧)
prev parent reply other threads:[~2015-04-17 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 11:46 Yao Qi
2015-04-14 15:01 ` Pedro Alves
2015-04-14 16:06 ` Yao Qi
2015-04-14 16:36 ` Pedro Alves
2015-04-17 9:34 ` Yao Qi [this message]
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=86oamnrtdi.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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