[Bug gdb/31088] gdb requires build directories to exist

["fche at redhat dot com" <sourceware-bugzilla@sourceware.org>]

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

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2023-11-29
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
                 CC|                            |fche at redhat dot com

--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
Some baby investigation with ubuntu 22.04 binaries, taking /bin/ls
as an example:

eu-readelf -w `debuginfod-find debuginfo /bin/ls`:

DWARF section [30] '.debug_info' at offset 0x438:
 [Offset]
 Compilation unit at offset 0:
 Version: 5, Abbreviation section offset: 4084, Address size: 8, Offset size: 4
 Unit type: partial (3)
 [     c]  partial_unit         abbrev: 50
           stmt_list            (sec_offset) 0
           comp_dir             (line_strp) "."


 Compilation unit at offset 3348:
 Version: 5, Abbreviation section offset: 0, Address size: 8, Offset size: 4
 Unit type: compile (1)
 [   d20]  compile_unit         abbrev: 43
           producer             (GNU_strp_alt) "GNU GIMPLE 11.2.0
-mtune=generic -march=x86-64 -g -g -O2 -O2 -fno-openmp -fno-openacc -fPIC
-fcf-protection=full -fstack-protector-strong -ffat-lto-objects -fltrans"
           language             (data1) C11 (29)
           name                 (line_strp) "<artificial>"
           comp_dir             (line_strp) "."


i.e., AT_comp_dir = "."

MJW advises this implicates https://dwarfstd.org/issues/210628.1.html ,
wherein it is acknowledged that absolute paths are expected, and offers
semantics to DWARF6 for special cases.  Those special cases would not
help at all in the debuginfod-supplied cases, where the file names in
the client cache have no relationship to the build system's file tree
or the installed location of the binary.

So the question is why are these binaries arriving with ".", seeing that
they were produced by GCC.

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