Automatically fetching Build ID from remote libraries and resole them locally?

Jan Kratochvil
Mon Mar 30 08:45:22 GMT 2020

On Mon, 30 Mar 2020 10:35:30 +0200, Norbert Lange via Gdb wrote:
> Currently its not possible to detect the Build ID without transferring the
> whole library from Remote target to the local gdb. I suppose with coredumps
> its a similar problem. What I would like is using build IDs wherever
> possible. That means retrieve them from the remote, and maybe define some
> fileformat to augment coredumps with the information.

Coredumps already contain build-ids of executables + shared libraries as long
as it is enabled (it is by default):
  - (bit 4) ELF header pages in file-backed private memory areas (it is
            effective only if the bit 2 is cleared)

build-id loading from remote files should be also somehow supported by recent
GDBs (done by Gary Benson).

Fedora+RHEL GDB has patchset
to locate appropriate executable + shared libraries from such core file by
build-id - it locates then through symlinks in:

IIUC that patchset should be now being replaced by the elfutils debuginfod.


More information about the Gdb mailing list