Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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-unaligned.exp on s390x
Date: Wed, 4 Mar 2026 07:40:18 +0100	[thread overview]
Message-ID: <8f572769-fb70-4250-8f31-6d0c6c166f92@suse.de> (raw)
In-Reply-To: <20260303221842.488050-1-kevinb@redhat.com>

On 3/3/26 11:17 PM, Kevin Buettner wrote:
> 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."
> 
> 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, with one nit.

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>

Thanks,
- Tom

> ---
>   gdb/testsuite/gdb.base/watchpoint-unaligned.exp | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/gdb/testsuite/gdb.base/watchpoint-unaligned.exp b/gdb/testsuite/gdb.base/watchpoint-unaligned.exp
> index d3bba6ae010..4b93dbf8234 100644
> --- a/gdb/testsuite/gdb.base/watchpoint-unaligned.exp
> +++ b/gdb/testsuite/gdb.base/watchpoint-unaligned.exp
> @@ -17,7 +17,7 @@
>   
>   # Test inserting read watchpoints on unaligned addresses.
>   
> -require allow_hw_watchpoint_tests
> +require allow_hw_watchpoint_tests allow_hw_watchpoint_access_tests
>   
>   standard_testfile
>   if { [prepare_for_testing ${testfile}.exp ${testfile} ${srcfile}] } {


  reply	other threads:[~2026-03-04  6:40 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 [this message]
2026-03-11  0:36   ` 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=8f572769-fb70-4250-8f31-6d0c6c166f92@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