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/31723] [gdb/testsuite] fission board and g3
Date: Wed, 15 May 2024 08:37:33 +0000 [thread overview]
Message-ID: <bug-31723-4717-QKjGTAPmI7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31723-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31723
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> (In reply to Tom de Vries from comment #0)
> > I managed to get it to pass by using gcc 14 on tumbleweed, I'm assuming some
> > gcc debuginfo bug got fixed.
>
> Hmm, we should enable complaints to see if that's actually the case, or if
> macro reading is cut short, similar to what happens here (PR 31725 comment
> 2).
Affirmative, with gcc 14 we get:
...
$ gdb -q -batch -iex "set complaints 100"
/data/vries/gdb/tumbleweed-20240416/build/gdb/testsuite/outputs/gdb.base/errno/errno-macros
-ex "b main"
During symbol reading: unrecognized DW_MACINFO or DW_MACRO opcode 0xbb
Breakpoint 1 at 0x40064a: file
/data/vries/gdb/src/gdb/testsuite/gdb.base/errno.c, line 24.
...
So gcc 14 is in fact not fixed, instead we bail out silently.
FWIW, I've fixed a fission-debug related bug in gcc (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115066 ). The fix will be
available in gcc 15.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-05-15 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 8:36 [Bug testsuite/31723] New: " vries at gcc dot gnu.org
2024-05-10 14:39 ` [Bug testsuite/31723] " vries at gcc dot gnu.org
2024-05-15 8:37 ` vries at gcc dot gnu.org [this message]
2024-05-22 6:29 ` 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-31723-4717-QKjGTAPmI7@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).