I posted a plea in the GDB mailing list:

https://sourceware.org/pipermail/gdb/2026-November/052368.html

In general it's problematic that the filename of the cached file is
lost / not available in the debuginfod cache.

As a result, due to the way GDB uses cached filenames, it is difficult
to discover critical information about loaded shared libraries (e.g.).

Of course the build ID has to be part of the path, so that we can
ensure uniqueness and locate the cached file.

But, would it be possible to replace the hardcoded "executable"
filename in the cached path with the actual name of the file?  I
realize this means during lookup we may have to do an opendir() and
find the file that way rather than using a well-known name.

Reply via email to