[Bug testsuite/31723] New: [gdb/testsuite] fission board and g3

[Bug testsuite/31723] New: [gdb/testsuite] fission board and g3

[vries at gcc dot gnu.org]

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

            Bug ID: 31723
           Summary: [gdb/testsuite] fission board and g3
           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: ---

I ran proposed test-case gdb.base/check-errno.exp with target board fission,
and ran into what might be a duplicate of PR24635.

This only happens for the -g3 binaries.

I managed to get it to pass by using gcc 14 on tumbleweed, I'm assuming some
gcc debuginfo bug got fixed.

We could require gcc 14 (in case gcc is used) in the fission target board, to
prevent running into these fails in various test-cases.

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

[Bug testsuite/31723] [gdb/testsuite] fission board and g3

[vries at gcc dot gnu.org]

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(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).

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

[Bug testsuite/31723] [gdb/testsuite] fission board and g3

[vries at gcc dot gnu.org]

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.

[Bug testsuite/31723] [gdb/testsuite] fission board and g3

[vries at gcc dot gnu.org]

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

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
I've submitted a bunch of fixes here:
https://sourceware.org/pipermail/gdb-patches/2024-May/209298.html .

After these will land, we can re-evaluate the idea of requiring a certain
compiler version.

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