Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Guinevere Larsen <guinevere@redhat.com>
Subject: Re: [PATCHv3] gdb: notify of inferior switch when needed from 'thread' command
Date: Mon, 04 May 2026 21:31:46 +0100	[thread overview]
Message-ID: <87wlxiex1p.fsf@redhat.com> (raw)
In-Reply-To: <3c8d246a5262fbb39a0f352498e1a2592061f478.1776437170.git.aburgess@redhat.com>

Andrew Burgess <aburgess@redhat.com> writes:

> I looked into the issues that Baris raised in this email:
>
>   https://inbox.sourceware.org/gdb-patches/IA0PR11MB7307BB4B5B3CC3A354289261C4C7A@IA0PR11MB7307.namprd11.prod.outlook.com
>
> About how in a multi-inferior debug session, if hitting a breakpoint
> triggers a thread AND inferior switch, then we announce the new
> thread, but not the new inferior.  This is very similar to the fix
> being proposed in this patch.
>
> However, in this case we don't use
> notify_user_selected_context_changed to announce the new
> thread/inferior, instead this is done in normal_stop (infrunc.c).
>
> I think we could and should change this code to announce the inferior
> switch where appropriate.  But given this change would be quite
> different to the changes in this patch, then my current plan is to do
> that in a follow up change once this is merged.
>
> Speaking of which, my current plan is to push this next week.  I don't
> think Pedro, who had feedback on V1, is actively reviewing patches any
> more, but if there's any feedback post-commit, I'm happy to discuss
> things then.
>
> In v3:
>
>   - Rebased and retested.
>
> In v2:
>
>   - Rebased and retested.
>
>   - Reworked commit message to try and address Pedro's concerns.

I've checked this in now.

Thanks,
Andrew


      parent reply	other threads:[~2026-05-04 20:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-08  8:48 [PATCH] " Andrew Burgess
2025-10-09 18:59 ` Pedro Alves
2025-10-10 14:47   ` Andrew Burgess
2025-11-03 16:12     ` Aktemur, Tankut Baris
2025-11-03 17:57       ` Andrew Burgess
2026-01-06 13:37     ` Andrew Burgess
2026-01-26 13:58 ` [PATCHv2] " Andrew Burgess
2026-03-17 19:41   ` Guinevere Larsen
2026-03-18 14:34     ` Andrew Burgess
2026-04-17 14:54   ` [PATCHv3] " Andrew Burgess
2026-04-24 10:15     ` Aktemur, Tankut Baris
2026-05-04 20:31     ` 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=87wlxiex1p.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@redhat.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