From: "Schimpe, Christina" <christina.schimpe@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "pedro@palves.net" <pedro@palves.net>,
"aburgess@redhat.com" <aburgess@redhat.com>,
"eliz@gnu.org" <eliz@gnu.org>, "tom@tromey.com" <tom@tromey.com>
Subject: Re: [PING][PATCH v3 0/3] Apply fixme notes for multi-target support
Date: Tue, 4 Oct 2022 12:40:39 +0000 [thread overview]
Message-ID: <CY4PR11MB20052BC3563B4C69D1B5CC81F95A9@CY4PR11MB2005.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220909153709.3687178-1-christina.schimpe@intel.com>
Kindly pinging.
Thanks,
Christina
________________________________
From: Schimpe, Christina <christina.schimpe@intel.com>
Sent: Friday, September 9, 2022 5:37 PM
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>
Cc: pedro@palves.net <pedro@palves.net>; aburgess@redhat.com <aburgess@redhat.com>; eliz@gnu.org <eliz@gnu.org>; tom@tromey.com <tom@tromey.com>; Schimpe, Christina <christina.schimpe@intel.com>
Subject: [PATCH v3 0/3] Apply fixme notes for multi-target support
Hi all,
this is the V3 for the series "Apply fixme notes for multi-target support".
Sorry again for taking so long to post the v3 of this series. This version
addresses Pedro's and Eli's comments and applies the logging for the
'set/show remote PACKET-NAME/memory-read/write-packet-size commands' as
discussed in https://sourceware.org/pipermail/gdb-patches/2022-June/189691.html.
V2 of this series can be found here:
https://sourceware.org/pipermail/gdb-patches/2022-March/187046.html.
Changes for patch #1:
* Adapt the code, commit message, news entry and documentation according to the
new way of configuration for remotes' feature packets using the
'set remote PACKET-NAME' commands.
* Adapt the logging for the 'show remote PACKET-NAME' and
'set remote PACKET-NAME' commands as discussed.
* Adapt tests for the new logging.
* Make logging i18n friendly.
Changes for patch #2:
* Adapt the code, commit message, news entry and documentation according to the
new way of configuration using the 'set remote memory-read/write-packet-size'
commands.
* Adapt the logging for the 'set remote memory-read/write-packet-size' commands
as discussed.
* Fix "Argument required" logging of the set remote
memory-read/write-packet-size commands.
* Adapt tests for the new logging.
I did not make any changes to patch #3 of this series, as it was already approved.
Thanks,
Christina
Christina Schimpe (3):
gdb: Make global feature array a per-remote target array
gdb: Add per-remote target variables for memory read and write config
gdb: Remove workaround for the vCont packet
gdb/NEWS | 21 +
gdb/doc/gdb.texinfo | 24 +-
gdb/remote.c | 1478 +++++++++--------
gdb/testsuite/gdb.base/cond-eval-mode.exp | 9 +-
gdb/testsuite/gdb.base/dprintf.exp | 5 +-
gdb/testsuite/gdb.base/find-unmapped.exp | 5 +-
.../gdb.base/hbreak-in-shr-unsupported.exp | 4 +-
gdb/testsuite/gdb.base/remote.exp | 49 +-
.../gdb.multi/multi-target-info-inferiors.exp | 6 +-
gdb/testsuite/gdb.multi/multi-target.exp.tcl | 8 +-
.../connect-without-multi-process.exp | 4 +-
.../gdb.server/exit-multiple-threads.exp | 9 +-
gdb/testsuite/gdb.server/ext-restart.exp | 5 +-
gdb/testsuite/gdb.server/ext-wrapper.exp | 5 +-
gdb/testsuite/gdb.server/server-exec-info.exp | 5 +-
gdb/testsuite/gdb.server/server-kill.exp | 4 +-
.../gdb.server/stop-reply-no-thread-multi.exp | 8 +-
.../gdb.server/stop-reply-no-thread.exp | 9 +-
.../process-dies-while-handling-bp.exp | 9 +-
gdb/testsuite/gdb.trace/change-loc.exp | 4 +-
gdb/testsuite/gdb.trace/qtro.exp | 6 +-
21 files changed, 980 insertions(+), 697 deletions(-)
--
2.25.1
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
WARNING: multiple messages have this Message-ID
From: "Schimpe, Christina" <christina.schimpe@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "pedro@palves.net" <pedro@palves.net>,
"aburgess@redhat.com" <aburgess@redhat.com>,
"eliz@gnu.org" <eliz@gnu.org>, "tom@tromey.com" <tom@tromey.com>
Subject: Re: [PING][PATCH v3 0/3] Apply fixme notes for multi-target support
Date: Tue, 4 Oct 2022 12:40:39 +0000 [thread overview]
Message-ID: <CY4PR11MB20052BC3563B4C69D1B5CC81F95A9@CY4PR11MB2005.namprd11.prod.outlook.com> (raw)
Message-ID: <20221004124039.3PrKFffvZJgss1VRKY0_yqoDWTpmp5TyvvhYv5LbLfQ@z> (raw)
In-Reply-To: <20220909153709.3687178-1-christina.schimpe@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3777 bytes --]
Kindly pinging.
Thanks,
Christina
________________________________
From: Schimpe, Christina <christina.schimpe@intel.com>
Sent: Friday, September 9, 2022 5:37 PM
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>
Cc: pedro@palves.net <pedro@palves.net>; aburgess@redhat.com <aburgess@redhat.com>; eliz@gnu.org <eliz@gnu.org>; tom@tromey.com <tom@tromey.com>; Schimpe, Christina <christina.schimpe@intel.com>
Subject: [PATCH v3 0/3] Apply fixme notes for multi-target support
Hi all,
this is the V3 for the series "Apply fixme notes for multi-target support".
Sorry again for taking so long to post the v3 of this series. This version
addresses Pedro's and Eli's comments and applies the logging for the
'set/show remote PACKET-NAME/memory-read/write-packet-size commands' as
discussed in https://sourceware.org/pipermail/gdb-patches/2022-June/189691.html.
V2 of this series can be found here:
https://sourceware.org/pipermail/gdb-patches/2022-March/187046.html.
Changes for patch #1:
* Adapt the code, commit message, news entry and documentation according to the
new way of configuration for remotes' feature packets using the
'set remote PACKET-NAME' commands.
* Adapt the logging for the 'show remote PACKET-NAME' and
'set remote PACKET-NAME' commands as discussed.
* Adapt tests for the new logging.
* Make logging i18n friendly.
Changes for patch #2:
* Adapt the code, commit message, news entry and documentation according to the
new way of configuration using the 'set remote memory-read/write-packet-size'
commands.
* Adapt the logging for the 'set remote memory-read/write-packet-size' commands
as discussed.
* Fix "Argument required" logging of the set remote
memory-read/write-packet-size commands.
* Adapt tests for the new logging.
I did not make any changes to patch #3 of this series, as it was already approved.
Thanks,
Christina
Christina Schimpe (3):
gdb: Make global feature array a per-remote target array
gdb: Add per-remote target variables for memory read and write config
gdb: Remove workaround for the vCont packet
gdb/NEWS | 21 +
gdb/doc/gdb.texinfo | 24 +-
gdb/remote.c | 1478 +++++++++--------
gdb/testsuite/gdb.base/cond-eval-mode.exp | 9 +-
gdb/testsuite/gdb.base/dprintf.exp | 5 +-
gdb/testsuite/gdb.base/find-unmapped.exp | 5 +-
.../gdb.base/hbreak-in-shr-unsupported.exp | 4 +-
gdb/testsuite/gdb.base/remote.exp | 49 +-
.../gdb.multi/multi-target-info-inferiors.exp | 6 +-
gdb/testsuite/gdb.multi/multi-target.exp.tcl | 8 +-
.../connect-without-multi-process.exp | 4 +-
.../gdb.server/exit-multiple-threads.exp | 9 +-
gdb/testsuite/gdb.server/ext-restart.exp | 5 +-
gdb/testsuite/gdb.server/ext-wrapper.exp | 5 +-
gdb/testsuite/gdb.server/server-exec-info.exp | 5 +-
gdb/testsuite/gdb.server/server-kill.exp | 4 +-
.../gdb.server/stop-reply-no-thread-multi.exp | 8 +-
.../gdb.server/stop-reply-no-thread.exp | 9 +-
.../process-dies-while-handling-bp.exp | 9 +-
gdb/testsuite/gdb.trace/change-loc.exp | 4 +-
gdb/testsuite/gdb.trace/qtro.exp | 6 +-
21 files changed, 980 insertions(+), 697 deletions(-)
--
2.25.1
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-10-04 12:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 15:37 [PATCH " 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
2022-10-04 12:40 ` Schimpe, Christina [this message]
2022-10-04 12:40 ` [PING][PATCH v3 0/3] Apply fixme notes for multi-target support 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=CY4PR11MB20052BC3563B4C69D1B5CC81F95A9@CY4PR11MB2005.namprd11.prod.outlook.com \
--to=christina.schimpe@intel.com \
--cc=aburgess@redhat.com \
--cc=eliz@gnu.org \
--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).