Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: Skip gdb.base/watchpoint-adjacent.exp on s390x
Date: Tue, 3 Mar 2026 14:45:39 -0700	[thread overview]
Message-ID: <20260303144539.517044b2@f42-zbm-amd> (raw)
In-Reply-To: <1165cf58-be02-4303-95d2-994fcc7a2651@suse.de>

On Tue, 3 Mar 2026 09:56:24 +0100
Tom de Vries <tdevries@suse.de> wrote:

> 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>

Thanks for the quick approval.  I've pushed it.

> 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]

Yes, I see this one too.  I'll take care of it.  Expect a patch sometime
soon...

Kevin


      reply	other threads:[~2026-03-03 21:46 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
2026-03-03 21:45   ` 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=20260303144539.517044b2@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