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 testsuite/31499] New: [gdb/testsuite, remote host] ERROR: Couldn't get python version
Date: Sat, 16 Mar 2024 12:05:37 +0000 [thread overview]
Message-ID: <bug-31499-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31499
Bug ID: 31499
Summary: [gdb/testsuite, remote host] ERROR: Couldn't get
python version
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With host board local-remote-host.exp and target board
remote-gdbserver-on-localhost, while trying to run the dap tests, I got:
...
Executing on host: /data/vries/gdb/leap-15-4/build/gdb/gdb -nw -nx -q -iex "set
height 0" -iex "set width 0" -iex "set debuginfod enabled off" -data-directory
/data/vries/gdb/leap-15-4/build/gdb/data-directory -batch -ex "python print
(sys.version_info\[0\], sys.version_info\[1\])" (timeout = 300)
builtin_spawn [open ...]^M
sh: -c: line 0: syntax error near unexpected token `('
sh: -c: line 0: `/data/vries/gdb/leap-15-4/build/gdb/gdb -nw -nx -q -iex set
height 0 -iex set width 0 -iex set debuginfod enabled off -data-directory
/data/vries/gdb/leap-15-4/build/gdb/data-directory -batch -ex python print
(sys.version_info[0], sys.version_info[1]) ; echo XYZ${?}ZYX'
ERROR: tcl error sourcing /data/vries/gdb/src/gdb/testsuite/gdb.dap/cwd.exp.
ERROR: Couldn't get python version
...
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2024-03-16 12:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-31499-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).