From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id C200E384AB42; Wed, 15 May 2024 08:37:33 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C200E384AB42
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1715762253;
	bh=bJyCxa9jvqNk5itTuwC+qNzxEljIK5IilTNxh517SRM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=LfAwLNyug4aA5TSmLswfEqVm8mhpG2R32Q34+svA9Gm6PX3PzN6ubyrDmynksHZn4
	 zCxQGC6K0mlIl5zU7qQy2PArWTZaNPaOEGeQ0MwFMvtDc+R8dsJoIUq/c/0KVNZQv1
	 Sp8b/IEjDOpK2VEbO2abfxyLdlSS89E+3QrMzkak=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-31723-4717-QKjGTAPmI7@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-31723-4717@http.sourceware.org/bugzilla/>
References: <bug-31723-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D31723

--- 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.
>=20
> 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/er=
rno/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=3D115066 ).  The fix will be
available in gcc 15.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=