public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/20684] MI commands with "--thread X" cause a switch of the user-selected thread
Date: Sat, 13 Jan 2024 23:26:51 +0000 [thread overview]
Message-ID: <bug-20684-4717-DjYe1gr0tL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20684-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20684
Hannes Domani <ssbssa at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |12.1
Resolution|--- |FIXED
Status|NEW |RESOLVED
CC| |ssbssa at sourceware dot org
--- Comment #4 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Sourceware Commits from comment #1)
> The master branch has been updated by Andrew Burgess
> <aburgess@sourceware.org>:
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;
> h=a9c82bc13cf8dd5d9076e746f744ee711eb55507
>
> commit a9c82bc13cf8dd5d9076e746f744ee711eb55507
> Author: Jan Vrany <jan.vrany@labware.com>
> Date: Wed Mar 2 13:23:30 2022 +0000
>
> gdb/mi: preserve user selected thread and frame when invoking MI commands
>
> Fix for PR gdb/20684. When invoking MI commands with --thread and/or
> --frame, the user selected thread and frame was not preserved:
Fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-01-13 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-20684-4717@http.sourceware.org/bugzilla/>
2022-03-08 16:57 ` cvs-commit at gcc dot gnu.org
2022-03-27 9:49 ` eliz at gnu dot org
2024-01-13 23:22 ` ssbssa at sourceware dot org
2024-01-13 23:26 ` ssbssa at sourceware dot org [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=bug-20684-4717-DjYe1gr0tL@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).