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 rust/26121] New: FAIL: gdb.rust/modules.exp: print ::TWENTY_THREE
Date: Tue, 16 Jun 2020 13:40:53 +0000 [thread overview]
Message-ID: <bug-26121-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26121
Bug ID: 26121
Summary: FAIL: gdb.rust/modules.exp: print ::TWENTY_THREE
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: rust
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With test-case gdb.rust/modules.exp, I run into:
...
(gdb) PASS: gdb.rust/modules.exp: setting breakpoint at *::f2
print ::TWENTY_THREE^M
No symbol '::modules::TWENTY_THREE' in current context^M
(gdb) FAIL: gdb.rust/modules.exp: print ::TWENTY_THREE
...
This is using:
...
$ rustc --version
rustc 1.43.0
...
The commit adding the test mentions:
...
(Note that there are unrelated failures with newer
versions of rustc; I will be addressing those separately.)
...
So, perhaps this FAIL is on of those unrelated failures.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-06-16 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 13:40 vries at gcc dot gnu.org [this message]
2020-06-29 11:29 ` [Bug rust/26121] " vries at gcc dot gnu.org
2020-07-05 15:40 ` vries at gcc dot gnu.org
2020-07-11 22:14 ` cvs-commit at gcc dot gnu.org
2020-07-11 22:15 ` tromey at sourceware dot org
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-26121-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).