From: "Schimpe, Christina" <christina.schimpe@intel.com>
To: Tom Tromey <tom@tromey.com>,
Christina Schimpe via Gdb-patches <gdb-patches@sourceware.org>
Cc: "pedro@palves.net" <pedro@palves.net>
Subject: RE: [PATCH v3 3/3] gdb: Remove workaround for the vCont packet
Date: Wed, 21 Dec 2022 07:42:03 +0000 [thread overview]
Message-ID: <CY4PR11MB2005668DFF52721F64E699DDF9EB9@CY4PR11MB2005.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87pmcdkedt.fsf@tromey.com>
Hi Tom,
I am just working on a V4 of this series and will post it soon.
Christina
> -----Original Message-----
> From: Tom Tromey <tom@tromey.com>
> Sent: Tuesday, December 20, 2022 9:30 PM
> To: Christina Schimpe via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Schimpe, Christina <christina.schimpe@intel.com>; tom@tromey.com;
> pedro@palves.net
> Subject: Re: [PATCH v3 3/3] gdb: Remove workaround for the vCont packet
>
> >>>>> "Christina" == Christina Schimpe via Gdb-patches <gdb-
> patches@sourceware.org> writes:
>
> Christina> The workaround for the vCont packet is no longer required due
> Christina> to the former commit "gdb: Make global feature array a per-
> remote target array".
> Christina> The vCont packet is now checked once when the connection is
> Christina> started and the supported vCont actions are set to the
> Christina> target's remote state attribute.
>
> Hi. I was curious, what's the status of this series?
>
> Tom
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2022-12-21 7:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 15:37 [PATCH v3 0/3] Apply fixme notes for multi-target support Christina Schimpe
2022-09-09 15:37 ` [PATCH v3 1/3] gdb: Make global feature array a per-remote target array Christina Schimpe
2022-10-04 13:48 ` Pedro Alves
2022-10-18 10:26 ` Schimpe, Christina
2022-09-09 15:37 ` [PATCH v3 2/3] gdb: Add per-remote target variables for memory read and write config Christina Schimpe
2022-09-09 15:57 ` Eli Zaretskii
2022-09-09 15:37 ` [PATCH v3 3/3] gdb: Remove workaround for the vCont packet Christina Schimpe
2022-12-20 20:29 ` Tom Tromey
2022-12-21 7:42 ` Schimpe, Christina [this message]
2022-10-04 12:40 ` [PING][PATCH v3 0/3] Apply fixme notes for multi-target support Schimpe, Christina
2022-10-04 12:40 ` Schimpe, Christina
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=CY4PR11MB2005668DFF52721F64E699DDF9EB9@CY4PR11MB2005.namprd11.prod.outlook.com \
--to=christina.schimpe@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).