From: Tom de Vries <tdevries@suse.de>
To: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: Skip gdb.base/watchpoint-adjacent.exp on s390x
Date: Tue, 3 Mar 2026 09:56:24 +0100 [thread overview]
Message-ID: <1165cf58-be02-4303-95d2-994fcc7a2651@suse.de> (raw)
In-Reply-To: <20260303024718.486406-1-kevinb@redhat.com>
On 3/3/26 3:46 AM, Kevin Buettner wrote:
> The watchpoint-adjacent.exp test requires both read and write hardware
> watchpoints. s390x only supports write watchpoints, causing 108 test
> failures when rwatch commands fail with "Target does not support this
> type of hardware watchpoint."
>
> Add a require for allow_hw_watchpoint_access_tests to skip this test on
> architectures without read watchpoint support.
Hi Kevin,
thanks for fixing this, LGTM.
Approved-By: Tom de Vries <tdevries@suse.de>
BTW, it looks like this needs a similar fix:
...
(gdb) rwatch data.u.size8twice[0]^M
Target does not support this type of hardware watchpoint.^M
(gdb) FAIL: gdb.base/watchpoint-unaligned.exp: fun=read_size8twice:
offset=0: index=0: rwatch data.u.size8twice[0]
...
Thanks,
- Tom
> ---
> gdb/testsuite/gdb.base/watchpoint-adjacent.exp | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gdb/testsuite/gdb.base/watchpoint-adjacent.exp b/gdb/testsuite/gdb.base/watchpoint-adjacent.exp
> index 901a383c5b5..3c3316059ad 100644
> --- a/gdb/testsuite/gdb.base/watchpoint-adjacent.exp
> +++ b/gdb/testsuite/gdb.base/watchpoint-adjacent.exp
> @@ -20,7 +20,7 @@
> # Multiple inferiors are compiled, using a variety of types for the
> # two fields.
>
> -require allow_hw_watchpoint_multi_tests
> +require allow_hw_watchpoint_multi_tests allow_hw_watchpoint_access_tests
>
> standard_testfile
>
next prev parent reply other threads:[~2026-03-03 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 2:46 Kevin Buettner
2026-03-03 8:56 ` Tom de Vries [this message]
2026-03-03 21:45 ` Kevin Buettner
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=1165cf58-be02-4303-95d2-994fcc7a2651@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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