From: Lancelot SIX <Lancelot.Six@amd.com>
To: Tankut Baris Aktemur <tankutbaris.aktemur@amd.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: fix regexp in gdb.rocm/watchpoint-at-end-of-shader.exp
Date: Wed, 20 May 2026 12:13:33 +0100 [thread overview]
Message-ID: <c5a23fd4-8fb2-4db2-97cf-dcc427ecb24c@amd.com> (raw)
In-Reply-To: <20260520091346.1332979-1-tankutbaris.aktemur@amd.com>
Hi,
Thanks for fixing this.
On 20/05/2026 10:13, Tankut Baris Aktemur wrote:
> The following tests fail:
>
> FAIL: gdb.rocm/watchpoint-at-end-of-shader.exp: precise_memory=on: continue
> FAIL: gdb.rocm/watchpoint-at-end-of-shader.exp: precise_memory=off: continue
>
> The reason is a difference in outputs seen in upstream and downstream
> branches. Fix the regexps to avoid the failures.
> ---
> gdb/testsuite/gdb.rocm/watchpoint-at-end-of-shader.exp | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.rocm/watchpoint-at-end-of-shader.exp b/gdb/testsuite/gdb.rocm/watchpoint-at-end-of-shader.exp
> index ff233c8b26a..ea88c1269b7 100644
> --- a/gdb/testsuite/gdb.rocm/watchpoint-at-end-of-shader.exp
> +++ b/gdb/testsuite/gdb.rocm/watchpoint-at-end-of-shader.exp
> @@ -71,9 +71,9 @@ proc do_test {precise_memory has_xfail} {
> setup_xfail "*-*-*"
> }
> gdb_test "continue" \
> - [multi_line "Switching to thread $::decimal, lane 0.*" \
> + [multi_line "Switching to \[^\r\n\]+(?=\r\n)" \
Wouldn't a simple "$" work rather than the look-ahead "(?=\r\n)"?
Anyway, both should be ok.
Best,
Lancelot.
Approved-by: Lancelot Six <lancelot.six@amd.com> (amdgpu)
> "" \
> - "Thread $::decimal \".*\" hit Hardware watchpoint $::decimal: -location \\*v" \
> + "Thread $::decimal \[^\r\n\]*hit Hardware watchpoint $::decimal: -location \\*v" \
> "" \
> "Old value = 64" \
> "New value = 8" \
next prev parent reply other threads:[~2026-05-20 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 9:13 Tankut Baris Aktemur
2026-05-20 11:13 ` Lancelot SIX [this message]
2026-05-20 11:26 ` Aktemur, Baris
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=c5a23fd4-8fb2-4db2-97cf-dcc427ecb24c@amd.com \
--to=lancelot.six@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=tankutbaris.aktemur@amd.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