[Bug symtab/31897] New: [gdb/symtab] FAIL: gdb.base/fission-macro.exp: dwarf_version=5: dwarf_bits=32: strict_dwarf=0: info macro FIRST

[Bug symtab/31897] New: [gdb/symtab] FAIL: gdb.base/fission-macro.exp: dwarf_version=5: dwarf_bits=32: strict_dwarf=0: info macro FIRST

[vries at gcc dot gnu.org]

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

            Bug ID: 31897
           Summary: [gdb/symtab] FAIL: gdb.base/fission-macro.exp:
                    dwarf_version=5: dwarf_bits=32: strict_dwarf=0: info
                    macro FIRST
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Here ( https://linaro.atlassian.net/browse/GNU-1258 ) the following FAIL is
reported on arm-linux:
...
(gdb) info macro FIRST
Defined at
/home/tcwg-buildslave/workspace/tcwg_gnu_2/abe/snapshots/gdb.git~master/gdb/testsuite/gdb.base/fission-macro.c:0
-DFIRST=1
(gdb) FAIL: gdb.base/fission-macro.exp: dwarf_version=5: dwarf_bits=32:
strict_dwarf=0: info macro FIRST
...

In contrast, on x86_64-linux I see:
...
(gdb) info macro FIRST^M
Defined at /data/vries/gdb/src/gdb/testsuite/gdb.base/fission-macro.c:18^M
#define FIRST 1^M
(gdb) PASS: gdb.base/fission-macro.exp: dwarf_version=5: dwarf_bits=32:
strict_dwarf=0: info macro FIRST
...

So, the line number for the macro definition seems to be incorrect: 0 instead
of 18, and consequently we get "-DFIRST=1" instead of "#define FIRST 1".

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

[Bug symtab/31897] [gdb/symtab] FAIL: gdb.base/fission-macro.exp: dwarf_version=5: dwarf_bits=32: strict_dwarf=0: info macro FIRST

[vries at gcc dot gnu.org]

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
I managed to reproduce this by building gcc from trunk on arm-linux, and
compiling the source file like this:
...
$ /home/linux/gcc/install/bin/gcc
/home/linux/gdb/src/gdb/testsuite/gdb.base/fission-macro.c -c -gsplit-dwarf
-gdwarf-5 -g3
...
and then doing:
...
$ gdb -q -batch fission-macro.o -ex "info macros fission-macro.c:25" 2>&1 |
grep -B1 FIRST
Defined at /home/linux/gdb/src/gdb/testsuite/gdb.base/fission-macro.c:0
-DFIRST=1
...

That however is fixed by "[gdb/macros] Handle 64-bit dwarf in
gdb.base/fission-macro.exp" (
https://sourceware.org/pipermail/gdb-patches/2024-May/209297.html ):
...
$ gdb -q -batch fission-macro.o -ex "info macros fission-macro.c:25" 2>&1 |
grep -B1 FIRST
Defined at /home/linux/gdb/src/gdb/testsuite/gdb.base/fission-macro.c:18
#define FIRST 1
...
and that stays the same if we apply the entire patch series.

However, that changes when we use a relative patch name for the source file:
...
$ /home/linux/gcc/install/bin/gcc src/gdb/testsuite/gdb.base/fission-macro.c -c
-gsplit-dwarf -gdwarf-5 -g3
...

The same problem occurs, and the same patch fixes it, but after applying
"[gdb/macros] Fix gdb.base/fission-macro.exp with clang" from that series, we
get another problem:
...
$ gdb -q -batch -iex "set complaints 1000" fission-macro.o -ex "info macros
fission-macro.c:25"
During symbol reading: debug info gives source 2 included from file at zero
line 0
During symbol reading: symtab found for
`src/gdb/testsuite/gdb.base/fission-macro.c', but that file
is not covered in the compilation unit's macro information
$
...

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