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 ada/28180] New: FAIL: gdb.ada/interface.exp: print s (timeout)
Date: Mon, 02 Aug 2021 22:32:28 +0000 [thread overview]
Message-ID: <bug-28180-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28180
Bug ID: 28180
Summary: FAIL: gdb.ada/interface.exp: print s (timeout)
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: ada
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With current master I noticed this timeout:
...
(gdb) PASS: gdb.ada/interface.exp: print r
print s^M
Multiple matches for s^M
[0] cancel^M
[1] s at
/home/vries/gdb_versions/devel/binutils-gdb.git/gdb/testsuite/gdb.ada/interface/foo.adb:20^M
[2] s at
/home/vries/gdb_versions/devel/binutils-gdb.git/gdb/testsuite/gdb.ada/interface/foo.adb:?^M
> FAIL: gdb.ada/interface.exp: print s (timeout)
...
Bisects to:
...
commit ba8694b650b60c29126fd958575ffa1ca4f6c415 (HEAD)
Author: Tom Tromey <tromey@adacore.com>
Date: Thu Jul 1 08:55:15 2021 -0600
Handle type qualifier for enumeration name
Pierre-Marie noticed that the Ada expression "TYPE'(NAME)" resolved
incorrectly when "TYPE" was an enumeration type. Here, "NAME" should
be unambiguous.
This patch fixes this problem. Note that the patch is not perfect --
it does not give an error if TYPE is an enumeration type but NAME is
not an enumerator but does have some other meaning in scope. Fixing
this proved difficult, and so I've left it out.
...
Fails with gcc-7.5.0, 8.5.0, passes with gcc-9.3.1, gcc-10.3.1, gcc-11.1.1.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-08-02 22:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 22:32 vries at gcc dot gnu.org [this message]
2021-08-02 22:32 ` [Bug ada/28180] " vries at gcc dot gnu.org
2021-08-02 22:36 ` vries at gcc dot gnu.org
2021-08-03 21:03 ` tromey at sourceware dot org
2021-08-04 20:06 ` tromey at sourceware dot org
2021-08-05 10:11 ` vries at gcc dot gnu.org
2021-08-05 10:56 ` vries at gcc dot gnu.org
2021-08-05 13:03 ` vries at gcc dot gnu.org
2021-08-05 13:17 ` vries at gcc dot gnu.org
2021-08-05 15:04 ` vries at gcc dot gnu.org
2021-08-06 16:16 ` tromey at sourceware dot org
2021-08-08 8:35 ` vries at gcc dot gnu.org
2021-08-13 18:42 ` tromey at sourceware dot org
2021-08-13 18:53 ` tromey at sourceware dot org
2021-08-14 13:13 ` vries at gcc dot gnu.org
2021-08-14 14:36 ` vries at gcc dot gnu.org
2021-08-17 18:05 ` brobecker at gnat dot com
2021-08-17 20:08 ` tromey at sourceware dot org
2021-08-24 11:14 ` vries at gcc dot gnu.org
2021-10-05 11:18 ` vries at gcc dot gnu.org
2024-03-08 9:55 ` sam at gentoo 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-28180-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).