From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Tom de Vries <tdevries@suse.de>
Subject: Re: [PATCH] gdb/testsuite: Skip gdb.base/watchpoint-unaligned.exp on s390x
Date: Tue, 10 Mar 2026 17:36:20 -0700 [thread overview]
Message-ID: <20260310173620.26fce84a@f42-zbm-amd> (raw)
In-Reply-To: <8f572769-fb70-4250-8f31-6d0c6c166f92@suse.de>
On Wed, 4 Mar 2026 07:40:18 +0100
Tom de Vries <tdevries@suse.de> wrote:
> While indeed the comment at the top mentions read watchpoints, the
> test-case contains some hardcoded downgrading to regular watchpoints for
> [istarget "s390*-*-*"], and consequently most of the test-case passes on
> s390x.
>
> It's only the last bit (which runs size8twice) that fails, so moving the
> check here:
> ...
> + if {![allow_hw_watchpoint_access_tests]} {
> + continue
> + }
> set cmd "rwatch"
> ...
> is a more minimal fix, in the sense that it only skips the failing test.
>
> Approved-By: Tom de Vries <tdevries@suse.de>
Agreed; that is a better way to do it. After testing, this is what I pushed:
gdb/testsuite: Skip rwatch in watchpoint-unaligned.exp on s390x
The watchpoint-unaligned.exp test requires both read and write
hardware watchpoints. s390x only supports write watchpoints, causing
one test failure when the rwatch command fails with "Target does not
support this type of hardware watchpoint."
This commit causes the test using the rwatch command in this file to
be skipped when allow_hw_watchpoint_access_tests is false.
Co-Authored-By: Tom de Vries <tdevries@suse.de>
Approved-By: Tom de Vries <tdevries@suse.de>
diff --git a/gdb/testsuite/gdb.base/watchpoint-unaligned.exp b/gdb/testsuite/gdb.base/watchpoint-unaligned.exp
index d3bba6ae010..8b929e5de4e 100644
--- a/gdb/testsuite/gdb.base/watchpoint-unaligned.exp
+++ b/gdb/testsuite/gdb.base/watchpoint-unaligned.exp
@@ -219,6 +219,9 @@ foreach_with_prefix fun { write_size8twice read_size8twice } {
if { $fun == "write_size8twice" } {
set cmd "watch"
} else {
+ if {![allow_hw_watchpoint_access_tests]} {
+ continue
+ }
set cmd "rwatch"
}
foreach_with_prefix offset { 0 1 } {
prev parent reply other threads:[~2026-03-11 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 22:17 Kevin Buettner
2026-03-04 6:40 ` Tom de Vries
2026-03-11 0:36 ` Kevin Buettner [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=20260310173620.26fce84a@f42-zbm-amd \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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