public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCHv2 0/2] Fixing regression in mi -add-inferior command
Date: Wed,  2 Mar 2022 11:57:34 +0000	[thread overview]
Message-ID: <cover.1646221667.git.aburgess@redhat.com> (raw)
In-Reply-To: <OS3PR01MB629131B83CD4E907BCD7F6A2FB3D9@OS3PR01MB6291.jpnprd01.prod.outlook.com>

Hi Muhammad,

Thanks for working on this.  I've taken your patch and incorporated it
into the two patch series below, the first patch is still credited to
you, but has some changes:

 - During testing I noticed that with your patch, after -add-inferior,
   the new inferior has become the selected inferior.  I believe this
   was not the case before the original mutli-target patch, and isn't
   the case for the CLI command, so I fixed this, and extended the
   testing to cover this case.

 - I've moved the comment for switch_to_inferior_and_push_target into
   the .h file, and updated the .c file to match inline with the GDB
   style.

 - I tightened some of the pattern matching in the test case, for
   example, parsing the 'info inferiors' output to create an expected
   pattern for the connection name of the new inferior.

 - I tweaked the commit message to directly reference the commit that
   introduced the regression, I think this helps for anyone in the
   future trying to track down the history of a particular change.

Then I added a second commit that adds the --no-connection option for
the -add-inferior command.  I felt that it was important that these
two changes go in as a single series as, after the first commit, we
effectively loose the ability to create a new inferior with no
connection.

I'd welcome your feedback on both patches.  I think we just need to
wait for a doc review on patch #2, then we can probably get this
merged.

Thanks,
Andrew

---

Andrew Burgess (1):
  gdb/mi: add --no-connection to MI -add-inferior command

Muhammad Umair Sair via Gdb-patches (1):
  gdb/mi: fix regression in mi -add-inferior command

 gdb/doc/gdb.texinfo                      |  39 ++++++-
 gdb/inferior.c                           |   6 +-
 gdb/inferior.h                           |   7 ++
 gdb/mi/mi-main.c                         |  47 +++++++-
 gdb/testsuite/gdb.mi/mi-add-inferior.exp | 130 +++++++++++++++++++++++
 5 files changed, 217 insertions(+), 12 deletions(-)
 create mode 100644 gdb/testsuite/gdb.mi/mi-add-inferior.exp

-- 
2.25.4


  reply	other threads:[~2022-03-02 11:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 17:25 [PATCH] " Muhammad Umair Sair
2022-03-02 11:57 ` Andrew Burgess [this message]
2022-03-02 11:57   ` [PATCHv2 1/2] gdb/mi: fix " Andrew Burgess
2022-03-02 11:57   ` [PATCHv2 2/2] gdb/mi: add --no-connection to MI " Andrew Burgess
2022-03-02 20:01     ` Eli Zaretskii
2022-03-03 12:44       ` Andrew Burgess
2022-03-03 14:02         ` Eli Zaretskii
2022-03-03 14:58         ` Pedro Alves
2022-03-07 19:40           ` Andrew Burgess
2022-03-07 20:37             ` Pedro Alves
2022-03-08 12:55               ` Andrew Burgess
2022-03-08 20:41                 ` Pedro Alves
2022-03-08 12:58               ` [PUSHED 0/2] Fixing regression in mi " Andrew Burgess
2022-03-08 12:58                 ` [PUSHED 1/2] gdb/mi: fix " Andrew Burgess
2022-03-08 12:58                 ` [PUSHED 2/2] gdb/mi: add --no-connection to MI " Andrew Burgess
2022-03-03 14:59   ` [PATCHv2 0/2] Fixing regression in mi " Pedro Alves

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=cover.1646221667.git.aburgess@redhat.com \
    --to=aburgess@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).