From: Lancelot SIX <Lancelot.Six@amd.com>
To: "Aktemur, Baris" <TankutBaris.Aktemur@amd.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb/testsuite: fix gdb.rocm/interrupt-twice
Date: Fri, 3 Jul 2026 11:58:56 +0100 [thread overview]
Message-ID: <48613917-c292-4198-ae3d-8f6dd2c59ff1@amd.com> (raw)
In-Reply-To: <DM4PR12MB64700B3EDB9244C1F8762194F8F62@DM4PR12MB6470.namprd12.prod.outlook.com>
On 01/07/2026 17:34, Aktemur, Baris wrote:
> AMD General
>
> On Wednesday, July 1, 2026 6:19 PM, Six, Lancelot wrote:
>> Since 246aecb1cd1 "gdb/testsuite: make gdb_breakpoint, runto and
>> runto_main use parse_args", gdb_breakpoint arguments changed. The
>> gdb.rocm/interrupt-twice.exp testcase was not updated to call
>> gdb_breakpoint with correct arguments. This due to the new test being
>> reviewed before the gdb_breakpoint landed, but it being pushed after.
>>
>> This patch fixes this issue.
>>
>> Change-Id: I0204e2c3cc9b704c79ce01386134e13b018593b8
>> ---
>> gdb/testsuite/gdb.rocm/interrupt-twice.exp | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/gdb/testsuite/gdb.rocm/interrupt-twice.exp
>> b/gdb/testsuite/gdb.rocm/interrupt-twice.exp
>> index bdaa3babe16..0e87b5c66e8 100644
>> --- a/gdb/testsuite/gdb.rocm/interrupt-twice.exp
>> +++ b/gdb/testsuite/gdb.rocm/interrupt-twice.exp
>> @@ -33,7 +33,7 @@ with_rocm_gpu_lock {
>> clean_restart $::testfile
>> }
>>
>> - gdb_breakpoint "loop" {allow-pending} {temporary}
>> + gdb_breakpoint "loop" -allow-pending -temporary
>
> Thank you for fixing this. LGTM.
>
> Reviewed-By: Tankut Baris Aktemur <TankutBaris.Aktemur@amd.com>
>
> -Baris
>
>
Thanks.
Pushed as 674d984dd02.
Best,
Lancelot.
prev parent reply other threads:[~2026-07-03 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 16:18 Lancelot SIX
2026-07-01 16:34 ` Aktemur, Baris
2026-07-03 10:58 ` Lancelot SIX [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=48613917-c292-4198-ae3d-8f6dd2c59ff1@amd.com \
--to=lancelot.six@amd.com \
--cc=TankutBaris.Aktemur@amd.com \
--cc=gdb-patches@sourceware.org \
/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