public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Christina Schimpe <christina.schimpe@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/3] gdb: Make global feature array a per-remote target array
Date: Tue, 29 Mar 2022 16:45:08 +0300	[thread overview]
Message-ID: <83r16k98kb.fsf@gnu.org> (raw)
In-Reply-To: <20220329131158.3970228-2-christina.schimpe@intel.com> (message from Christina Schimpe via Gdb-patches on Tue, 29 Mar 2022 15:11:56 +0200)

> Date: Tue, 29 Mar 2022 15:11:56 +0200
> From: Christina Schimpe via Gdb-patches <gdb-patches@sourceware.org>
> 
>  gdb/NEWS                                      |   13 +
>  gdb/doc/gdb.texinfo                           |   10 +-
>  gdb/remote.c                                  | 1057 ++++++++++-------
>  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.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 +-
>  20 files changed, 695 insertions(+), 490 deletions(-)

The documentation parts are OK, thanks.

  reply	other threads:[~2022-03-29 13:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 13:11 [PATCH v2 0/3] Apply fixme notes for multi-target support Christina Schimpe
2022-03-29 13:11 ` [PATCH v2 1/3] gdb: Make global feature array a per-remote target array Christina Schimpe
2022-03-29 13:45   ` Eli Zaretskii [this message]
2022-04-18 14:56   ` Tom Tromey
2022-04-18 19:01   ` Pedro Alves
2022-04-20 11:30     ` "show remote foo-packet" regression (Re: [PATCH v2 1/3] gdb: Make global feature array a per-remote target array) Pedro Alves
2022-04-20 11:31     ` Pedro Alves
2022-04-21 10:25       ` Andrew Burgess
2022-04-21 10:31         ` Pedro Alves
2022-04-21 11:01           ` Andrew Burgess
2022-04-21 16:28             ` Andrew Burgess
2022-04-21 18:20               ` Pedro Alves
2022-04-27 13:55     ` [PATCH v2 1/3] gdb: Make global feature array a per-remote target array Schimpe, Christina
2022-05-25 14:27       ` Pedro Alves
2022-06-01 10:45         ` Schimpe, Christina
2022-03-29 13:11 ` [PATCH v2 2/3] gdb: Add per-remote target variables for memory read and write config Christina Schimpe
2022-03-29 13:48   ` Eli Zaretskii
2022-04-18 14:56   ` Tom Tromey
2022-03-29 13:11 ` [PATCH v2 3/3] gdb: Remove workaround for the vCont packet Christina Schimpe
2022-04-18 14:59   ` Tom Tromey

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=83r16k98kb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=christina.schimpe@intel.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).