debuginfod: why can't it save real filenames??

[Paul Smith via Gdb <gdb@sourceware.org>]

When I first started using debuginfod support in GDB I was delighted as
it made things much simpler.

But, the more I use it the more frustrated I am finding one specific
aspect of it: there is no possible way (that I have discovered) to
figure out what the actual library (or binary) name is, that I'm
debugging with!  It's quite infuriating.

For example, if I run "info shared" I'm treated to an incomprehensible
set of buildid-based pathnames from my cache, like:

From      To        Syms   Shared Object Library
0x00007f  0x00007f  Yes    /home/me/.cache/debuginfod_client/c1ce8a211.../executable
0x00007f  0x00007f  Yes    /home/me/.cache/debuginfod_client/b86ba1ea9.../executable

This is not useful.  Even things like "info symbol xyz" show the
buildid path rather than the library name.  And if I run backtrace then
the name of the library where the symbol appears is also this
unintelligible value.

Of course, I understand that the directory name is the build ID value
and that it's how we ensure uniqueness so it's required, but why can't
the static filename "executable" be changed to the name of the library
or program that is being represented?  Then it would be easy enough to
understand.

E.g, instead of:

  ~/.cache/debuginfod_client/1234567890.../executable

couldn't we have:

  ~/.cache/debuginfod_client/1234567890.../libsyslookup.so

?


Is this a limitation of the debuginfod client?  Something GDB is doing?
Or is there an option or facility to make this better that I haven't
been able to find?

Thanks for listening!