[Bug symtab/30871] New: [gdb/symtab] Means to control finding debuginfo (without/with sysroot prefix)

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

            Bug ID: 30871
           Summary: [gdb/symtab] Means to control finding debuginfo
                    (without/with sysroot prefix)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

As documented here (
https://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html ), there
are two ways to find debuginfo:
- build-id, and
- debug link.

The build-id is tried first, then the debug link.

Then each case also tries first without, then with sysroot prefix.

Together this results in 4 different ways to get to the debuginfo.

AFAIK, in the test-suite we have test-cases that exercise the build-id and
debug link scenarios individually.

But that's not the case for the without/with sysroot prefix cases.

It would be good to have a way (say a maintenance command) that determines the
ways in which debug info can be found.

That way we could enforce using the with sysroot case.

[ This is relevant in the context of containers.  Say we have a container, with
an exec and corresponding debug info installed.  When we use gdb inside the
container to debug the exec, we find the debuginfo using the without sysroot
method.  When we try the same from outside the container, the without sysroot
method fails (because the debug info is installed in the container, not
outside) and falls back to the with sysroot method, which will look for the
debug info inside the container. ]

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