public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug ada/30908] [gdb/ada, gcc 13] FAIL: gdb.ada/str_binop_equal.exp: print my_str = "ABCD"
Date: Tue, 26 Sep 2023 15:37:36 +0000 [thread overview]
Message-ID: <bug-30908-4717-UcpjdLLAer@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30908-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30908
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
Do you have Ada system debug info installed?
I think there are various problems with overloading,
and the system debuginfo can trigger them.
Maybe this test can be rewritten to avoid this stuff.
I'd like to fix overloading but I'm told it is hard.
Haven't investigated yet for real.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-09-26 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 15:11 [Bug ada/30908] New: " vries at gcc dot gnu.org
2023-09-26 15:37 ` tromey at sourceware dot org [this message]
2023-09-26 17:14 ` [Bug ada/30908] " vries at gcc dot gnu.org
2023-09-26 23:31 ` vries at gcc dot gnu.org
2023-09-27 6:58 ` vries at gcc dot gnu.org
2023-10-01 13:26 ` vries at gcc dot gnu.org
2023-10-02 17:48 ` cvs-commit at gcc dot gnu.org
2024-02-26 18:38 ` tromey at sourceware dot org
2024-02-27 11:14 ` vries at gcc dot gnu.org
2024-02-27 11:23 ` vries at gcc dot gnu.org
2024-02-27 15:21 ` cvs-commit 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-30908-4717-UcpjdLLAer@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).