From: Pedro Alves <pedro@palves.net>
To: Andrew Burgess <aburgess@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv2 2/2] gdb/mi: add --no-connection to MI -add-inferior command
Date: Mon, 7 Mar 2022 20:37:02 +0000 [thread overview]
Message-ID: <0002f2a5-b503-ed36-c9af-1b392531863a@palves.net> (raw)
In-Reply-To: <87r17dwnzi.fsf@redhat.com>
On 2022-03-07 19:40, Andrew Burgess wrote:
> Pedro Alves <pedro@palves.net> writes:
>
>> On 2022-03-03 12:44, Andrew Burgess via Gdb-patches wrote:
>>> +* MI changes
>>> +
>>> + ** The '-add-inferior' command now accepts a '--no-connection'
>>> + option, which causes the new inferior to start without a
>>> + connection.
>>
>> I think this should also say that -add-inferior with no option now inherits
>> the connection of the current inferior, restoring the behavior of GDB xxx.
>
> I added this note, and pushed these two patches.
>
Hmm, I don't see any change in the pushed version. Forgot to amend the
patch, perhaps?
next prev parent reply other threads:[~2022-03-07 20:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 17:25 [PATCH] Fixing regression in mi " Muhammad Umair Sair
2022-03-02 11:57 ` [PATCHv2 0/2] " Andrew Burgess
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 [this message]
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=0002f2a5-b503-ed36-c9af-1b392531863a@palves.net \
--to=pedro@palves.net \
--cc=aburgess@redhat.com \
--cc=eliz@gnu.org \
--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).