public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: Norbert Lange <nolange79@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Automatically fetching Build ID from remote libraries and resole them locally?
Date: Fri, 27 Mar 2020 20:40:48 -0400	[thread overview]
Message-ID: <87blohl3an.fsf@redhat.com> (raw)
In-Reply-To: <CADYdroOCG1Ophut0yqh5qN544MEB1fVUGg90epPm-ewgnRuMEQ@mail.gmail.com> (Norbert Lange via Gdb's message of "Fri, 27 Mar 2020 15:20:21 +0100")


Norbert Lange via Gdb <gdb@sourceware.org> writes:

> [...]
> ie. DL only some ELF headers or remotely inspect the Build-ID,
> then lookup and resolve the matching library and debuginfo in the
> debug-file-directory database. [...]

By the way, this part of the problem is solved e.g. using the elfutils
debuginfod facility, which is now part of gdb.  If gdb can get the
buildids, then it can auto-download matching binaries & source code.

https://sourceware.org/elfutils/Debuginfod.html

- FChE


  reply	other threads:[~2020-03-28  0:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 14:20 Norbert Lange
2020-03-28  0:40 ` Frank Ch. Eigler [this message]
2020-03-30  8:35   ` Norbert Lange
2020-03-30  8:45     ` Jan Kratochvil
2020-03-30  9:04       ` Norbert Lange
2020-03-30  9:19         ` Jan Kratochvil
2020-03-30 18:43           ` Gary Benson
2020-04-06 11:31           ` Norbert Lange
2020-04-06 11:49             ` Jan Kratochvil
2020-04-06 12:08               ` Norbert Lange
2020-04-06 12:16                 ` Jan Kratochvil
2020-04-06 12:53                   ` Norbert Lange
2020-04-06 14:41                     ` Norbert Lange

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87blohl3an.fsf@redhat.com \
    --to=fche@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=nolange79@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).