From: "Zissulescu-Ianculescu, Claudiu" <Claudiu.Zissulescu-Ianculescu@amd.com>
To: Pedro Alves <pedro@palves.net>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "Six, Lancelot" <Lancelot.Six@amd.com>
Subject: RE: [PATCH] gdb: Remove redundant clear_proceed_status() call
Date: Wed, 17 Jun 2026 12:44:09 +0000 [thread overview]
Message-ID: <MW3PR12MB4394685FF47CBC41BBCFFA72ABE42@MW3PR12MB4394.namprd12.prod.outlook.com> (raw)
In-Reply-To: <49eeea9d-7fd7-4d31-99f5-3bef87c2e4ba@palves.net>
AMD General
Hi,
I'll respin the patch with Pedro's input.
Thank you,
Claudiu
-----Original Message-----
From: Pedro Alves <pedro@palves.net>
Sent: Tuesday, June 16, 2026 9:02 PM
To: Zissulescu-Ianculescu, Claudiu <Claudiu.Zissulescu-Ianculescu@amd.com>; gdb-patches@sourceware.org
Cc: Six, Lancelot <Lancelot.Six@amd.com>
Subject: Re: [PATCH] gdb: Remove redundant clear_proceed_status() call
[You don't often get email from pedro@palves.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
On 2026-06-16 15:55, Claudiu Zissulescu wrote:
> Remove redundant clear_proceed_status() call. The
> init_wait_for_inferior(), which runs on the very next line, already
> calls clear_proceed_status (0, false).
That call passes false, while this one did not. We know this actually fixes a bug in MI. Can you please update the commit log to describe that fix? A testcase would also be great. As far as I know, it wouldn't be complicated -- just a small test using -target-attach.
Pedro Alves
prev parent reply other threads:[~2026-06-17 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 14:55 Claudiu Zissulescu
2026-06-16 15:49 ` Simon Marchi
2026-06-16 18:01 ` Pedro Alves
2026-06-17 12:44 ` Zissulescu-Ianculescu, Claudiu [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=MW3PR12MB4394685FF47CBC41BBCFFA72ABE42@MW3PR12MB4394.namprd12.prod.outlook.com \
--to=claudiu.zissulescu-ianculescu@amd.com \
--cc=Lancelot.Six@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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