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: Thu, 17 Jun 2021 13:42:44 +0000	[thread overview]
Message-ID: <bug-27989-4717-TytYid3wAX@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 #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Simon Marchi <simark@sourceware.org>:

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

commit 18263be7565782a9c07045a7a72d80c507a5be09
Author: Simon Marchi <simon.marchi@efficios.com>
Date:   Thu Jun 17 09:41:59 2021 -0400

    gdb/testsuite: gdb.base/args.exp: add KFAIL for native-extended-gdbserver

    This test tests passing arguments made of exactly two single-quotes
    ('') or a single newline character through the --args argument of GDB.
    For some reason, GDB adds some extra single quotes when transmitting the
    arguments to GDBserver.  This produces some FAILs when testing with the
    native-extended-gdbserver board:

        FAIL: gdb.base/args.exp: argv[2] for one empty (with single quotes)
        FAIL: gdb.base/args.exp: argv[2] for two empty (with single quotes)
        FAIL: gdb.base/args.exp: argv[3] for two empty (with single quotes)
        FAIL: gdb.base/args.exp: argv[2] for one newline
        FAIL: gdb.base/args.exp: argv[2] for two newlines
        FAIL: gdb.base/args.exp: argv[3] for two newlines

    This is documented as PR 27989.  Add some appropriate KFAILs.

    gdb/testsuite/ChangeLog:

            * gdb.base/args.exp: Check target, KFAIL if remote.
            (args_test): Add parameter and use it.

    Change-Id: I49225d1c7df7ebaba480ebdd596df80f8fbf62f0

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

  parent reply	other threads:[~2021-06-17 13:42 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 [this message]
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
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-TytYid3wAX@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).