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/29782] New: [gdb/testsuite] FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=target:: action=permission: setup: adjust sysroot
Date: Mon, 14 Nov 2022 16:31:10 +0000 [thread overview]
Message-ID: <bug-29782-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29782
Bug ID: 29782
Summary: [gdb/testsuite] FAIL:
gdb.server/connect-with-no-symbol-file.exp:
sysroot=target:: action=permission: setup: adjust
sysroot
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: ---
On some aarch64 machine, I run into:
...
(gdb) PASS: gdb.server/connect-with-no-symbol-file.exp: sysroot=target::
action=permission: setup: disconnect
set sysroot target:^M
BFD: reopening
/suse/tdevries/gdb/build/gdb/testsuite/outputs/gdb.server/connect-with-no-symbol-file/.nfs00000000064b2e9200000180:
No such file or directory^M
(gdb) FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=target::
action=permission: setup: adjust sysroot
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-11-14 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 16:31 vries at gcc dot gnu.org [this message]
2022-11-16 15:57 ` [Bug testsuite/29782] " vries at gcc dot gnu.org
2024-02-02 15:37 ` cvs-commit at gcc dot gnu.org
2024-02-03 8:45 ` 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-29782-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).