Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH] gdb: new maintenance command to help debug remote argument issues
Date: Fri, 12 Sep 2025 16:56:41 -0700	[thread overview]
Message-ID: <20250912165641.7a5b1512@f41-zbm-amd> (raw)
In-Reply-To: <ce42cf51ef2ce5686f0f6e906311a136b485cec5.1757693139.git.aburgess@redhat.com>

On Fri, 12 Sep 2025 17:06:21 +0100
Andrew Burgess <aburgess@redhat.com> wrote:

> Add a new maintenance command 'maint test-remote-args', this command
> takes an argument string and splits it using gdb::remote_args::split
> and then joins the result using gdb::remote_args::join and prints all
> of the results.  This is useful for diagnosing problems with remote
> argument passing.
> 
> This new command is identical to what the remote argument self-tests
> do, but while I was working on improving remote argument passing it
> was far easier to have a command that I could just throw example
> strings at, rather than having to add new selftests and recompile
> GDB.
> 
> I ended up adding a couple of additional helper functions to the
> gdb::argv_vec class.
> 
> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
> Tested-By: Guinevere Larsen <guinevere@redhat.com>
> ---
>  gdb/NEWS                                      |  6 ++
>  gdb/doc/gdb.texinfo                           | 20 +++++++
>  gdb/remote.c                                  | 60 +++++++++++++++++++
>  .../gdb.base/maint-test-remote-args.exp       | 40 +++++++++++++
>  gdbsupport/gdb_argv_vec.h                     | 15 +++++
>  5 files changed, 141 insertions(+)
>  create mode 100644 gdb/testsuite/gdb.base/maint-test-remote-args.exp

LGTM.

Approved-By: Kevin Buettner <kevinb@redhat.com>


  reply	other threads:[~2025-09-12 23:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12 16:06 Andrew Burgess
2025-09-12 23:56 ` Kevin Buettner [this message]
2025-09-21 16:23   ` Andrew Burgess

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=20250912165641.7a5b1512@f41-zbm-amd \
    --to=kevinb@redhat.com \
    --cc=aburgess@redhat.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