From: Christina Schimpe <christina.schimpe@intel.com>
To: gdb-patches@sourceware.org
Cc: tom@tromey.com, pedro@palves.net, aburgess@redhat.com,
eliz@gnu.org, Christina Schimpe <christina.schimpe@intel.com>
Subject: [PATCH v4 0/3] Apply fixme notes for multi-target support
Date: Wed, 21 Dec 2022 14:39:55 +0100 [thread overview]
Message-ID: <20221221133958.2111768-1-christina.schimpe@intel.com> (raw)
Hi all,
this is the V4 for the series "Apply fixme notes for multi-target support".
It addresses Pedro's and Eli's latest comments.
V3 of this series can be found here:
https://sourceware.org/pipermail/gdb-patches/2022-September/191763.html.
Changes for patch #1:
* Split the struct packet_config into two structs packet_config and
packet_description to avoid unnecessary copies of a packet's name and title for
each new target. This requires a number of interface changes.
* Remove unnecessary show_cmd/set_cmd.
* Fix some nits.
Changes for patch #2:
* Fix documentation.
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 | 25 +-
gdb/remote.c | 1841 +++++++++--------
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 | 47 +-
.../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, 1136 insertions(+), 903 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 reply other threads:[~2022-12-21 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 13:39 Christina Schimpe [this message]
2022-12-21 13:39 ` [PATCH v4 1/3] gdb: Make global feature array a per-remote target array Christina Schimpe
2022-12-21 14:08 ` Eli Zaretskii
2023-01-23 17:42 ` Pedro Alves
2023-01-30 14:34 ` Schimpe, Christina
2022-12-21 13:39 ` [PATCH v4 2/3] gdb: Add per-remote target variables for memory read and write config Christina Schimpe
2022-12-21 14:13 ` Eli Zaretskii
2023-01-23 17:43 ` Pedro Alves
2023-01-30 14:34 ` Schimpe, Christina
2022-12-21 13:39 ` [PATCH v4 3/3] gdb: Remove workaround for the vCont packet Christina Schimpe
2023-01-23 17:46 ` Pedro Alves
2023-01-30 14:35 ` Schimpe, Christina
2023-01-16 8:58 ` [PING][PATCH v4 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=20221221133958.2111768-1-christina.schimpe@intel.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).