Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb: share some thread proceed related code between CLI and MI
Date: Mon, 24 Aug 2026 19:18:04 +0100	[thread overview]
Message-ID: <87pkz7tmar.fsf@redhat.com> (raw)
In-Reply-To: <75c88f8e-babb-4162-a941-424cb3bb1663@suse.de>

Tom de Vries <tdevries@suse.de> writes:

> On 8/7/26 5:31 PM, Andrew Burgess wrote:
>> Tom de Vries <tdevries@suse.de> writes:
>> 
>>> On 8/6/26 10:54 PM, Andrew Burgess wrote:
>>>> +	  if (inf == nullptr)
>>>> +	    proceed_all_threads ();
>>>> +	  else
>>>> +	    {
>>>> +	      for (thread_info &thread : inf->threads ())
>>>> +		proceed_one_thread (thread);
>>>>    	    }
>>>
>>> FWIW, also I wonder if it makes sense to fold this logic into
>>> proceed_all_threads:
>> 
>> I took a look through all the other proceed() calls and couldn't see
>> anything else that might want to share this code, so my preference would
>> be to leave things as I initially proposed.  I like the simpler each
>> function has one clear goal, rather than overloading proceed_all_threads
>> with multiple meanings ("all threads", or "all threads in inferior").
>> Especially not a fan of default arguments for cases like this (or in
>> general much).
>> 
>> That said, if you consider this a blocker to merging this patch then I
>> don't feel that strongly against it so would make the change to get this
>> fix merged.
>> 
>
> Hi Andrew,
>
> I don't consider this a blocker.

Great.

I've now pushed these patches.

Thanks,
Andrew


      reply	other threads:[~2026-08-24 18:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 20:53 [PATCH 0/2] Cleanup and bug fix related to thread iteration and proceed calls Andrew Burgess
2026-08-06 20:54 ` [PATCH 1/2] gdb: use inferior::threads instead of all_threads and a PID filter Andrew Burgess
2026-08-07  7:59   ` Tom de Vries
2026-08-06 20:54 ` [PATCH 2/2] gdb: share some thread proceed related code between CLI and MI Andrew Burgess
2026-08-07  9:20   ` Tom de Vries
2026-08-07 15:40     ` Andrew Burgess
2026-08-07 10:14   ` Tom de Vries
2026-08-07 15:31     ` Andrew Burgess
2026-08-07 16:52       ` Tom de Vries
2026-08-24 18:18         ` Andrew Burgess [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=87pkz7tmar.fsf@redhat.com \
    --to=aburgess@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