public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/28446] New: [native-extended-gdbserver] FAIL: gdb.base/a2-run.exp: run "a2-run" with shell (timeout)
Date: Tue, 12 Oct 2021 15:58:19 +0000 [thread overview]
Message-ID: <bug-28446-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28446
Bug ID: 28446
Summary: [native-extended-gdbserver] FAIL: gdb.base/a2-run.exp:
run "a2-run" with shell (timeout)
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: server
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
When running test-case gdb.base/a2-run.exp with target board
native-extended-gdbserver I run into:
...
(gdb) PASS: gdb.base/a2-run.exp: run "a2-run" again after setting args
run `echo 8`^M
^M
Child exited with status 0^M
Starting program:
/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/a2-run/a2-run
`echo 8`^M
Process
/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/a2-run/a2-run
created; pid = 18231^M
usage: factorial <number>^M
^M
Child exited with status 1^M
[Inferior 1 (process 18231) exited with code 01]^M
(gdb) FAIL: gdb.base/a2-run.exp: run "a2-run" with shell (timeout)
...
This is a regression since commit bea571ebd78 "Use construct_inferior_arguments
which handles special chars".
The commit adds escapes to the backticks, which then no longer are interpreted
by the shell.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-10-12 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 15:58 vries at gcc dot gnu.org [this message]
2021-10-12 16:02 ` [Bug server/28446] " vries at gcc dot gnu.org
2021-10-13 6:48 ` m.weghorn at posteo dot de
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-28446-4717@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).