public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27989] gdb.base/args.exp fails with native-extended-gdbserver board
Date: Fri, 06 Oct 2023 12:08:41 +0000	[thread overview]
Message-ID: <bug-27989-4717-m6lVqbUBx3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27989-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27989

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=67e6945b7e3a5c1577d19b9d83ee9be86c0a8424

commit 67e6945b7e3a5c1577d19b9d83ee9be86c0a8424
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Wed Sep 27 17:54:15 2023 +0100

    gdbserver: handle newlines in inferior arguments

    Similarly to how single quotes were mishandled, which was fixed two
    commits ago, this commit fixes handling of newlines in arguments
    passed to gdbserver.

    We already had a test that covered this, gdb.base/args.exp, which,
    when run with the native-extended-gdbserver board contained several
    KFAIL covering this situation.

    In this commit I remove the unnecessary, attempt to quote incoming
    newlines within arguments, and do some minimal cleanup of the related
    code.  There is additional cleanup that can be done, but I'm leaving
    that for the next commit.

    Then I've removed the KFAIL from the test case, and performed some
    minimal cleanup there too.

    After this commit the gdb.base/args.exp is 100% passing with the
    native-extended-gdbserver board file.

    During review I was pointed to this older series:

     
https://inbox.sourceware.org/gdb-patches/20211022071933.3478427-1-m.weghorn@posteo.de/

    which also includes this fix as part of a larger set of changes.  I'm
    giving a Co-Authored-By credit to the author of that original series.
    I believe this smaller fix brings some benefits on its own, though the
    original series does offer additional improvements.  Once this is
    merged I'll take a look at rebasing and resubmitting the original series.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27989

    Co-Authored-By: Michael Weghorn <m.weghorn@posteo.de>
    Approved-By: Tom Tromey <tom@tromey.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-10-06 12:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 18:45 [Bug gdb/27989] New: " simark at simark dot ca
2021-06-16 19:11 ` [Bug gdb/27989] " simark at simark dot ca
2021-06-17 13:42 ` cvs-commit at gcc dot gnu.org
2021-10-21 13:52 ` m.weghorn at posteo dot de
2023-10-06 12:08 ` cvs-commit at gcc dot gnu.org
2023-10-06 12:08 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-09 14:40 ` aburgess at redhat dot com

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=bug-27989-4717-m6lVqbUBx3@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).