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/29055] New: [gdb/testsuite] FAIL: gdb.ada/ghost.exp: print value (timeout)
Date: Wed, 13 Apr 2022 05:44:26 +0000 [thread overview]
Message-ID: <bug-29055-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29055
Bug ID: 29055
Summary: [gdb/testsuite] FAIL: gdb.ada/ghost.exp: print value
(timeout)
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 openSUSE Tumbleweed I run into:
...
(gdb) print value^M
Multiple matches for value^M
[0] cancel^M
[1] ada.strings.maps.value (<ref> ada.strings.maps.character_mapping;
character) return character at a-strmap.adb:317^M
[2] pck.value at
/data/vries/gdb_versions/devel/binutils-gdb.git/gdb/testsuite/gdb.ada/ghost/pck.ads:17^M
[3] system.object_reader.value (<ref> system.object_reader.object_symbol)
return system.object_reader.uint64 at s-objrea.adb:2274^M
[4] system.traceback.symbolic.value (system.address) return string at
s-trasym.adb:200^M
> FAIL: gdb.ada/ghost.exp: print value (timeout)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-04-13 5:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 5:44 vries at gcc dot gnu.org [this message]
2022-04-14 19:09 ` [Bug testsuite/29055] " tromey at sourceware dot org
2022-06-09 9:32 ` vries at gcc dot gnu.org
2022-06-09 22:01 ` tromey at sourceware dot org
2022-06-10 6:48 ` vries at gcc dot gnu.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-29055-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).