From: Arjan van de Ven <arjan@linux.intel.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
elfutils-devel@sourceware.org, patrick.mccarty@intel.com
Subject: Re: contrasting elfutils debuginfod and clr-debug-info server
Date: Fri, 07 Feb 2020 14:47:00 -0000 [thread overview]
Message-ID: <ae41db4d-fe4f-152f-6ebc-d17921e49eae@linux.intel.com> (raw)
In-Reply-To: <20200207091326.GK42691@wildebeest.org>
On 2/7/2020 1:13 AM, Mark Wielaard wrote:
> Hi,
>
> On Wed, Feb 05, 2020 at 02:05:42PM -0800, Arjan van de Ven wrote:
>> On 2/5/2020 11:14 AM, Frank Ch. Eigler wrote:
>>>>> clear-linux elfutils
>>>>>
>>>>> indexed by filename by buildid
>>>
>>>> actually the clear side provides both build id and filename, the
>>>> tools on the client (gdb and the like) try buildid first, and fall
>>>> back to filename, and we just do both
>>>
>>> AIUI that works by using the "/usr/lib/debug/.build-id/HE/XCODE" as the
>>> key, i.e., the build-id as a file name.
>>
>> sure but it's not "/usr/bin/true" of which you might have different versions over
>> the lifespan of a distro through its updates
>>
>> (e.g. you can connect gdb to a process that got updated on disk later and still get the right answers)
>
> Do you also handle the core file use case? There you might not have
> the right /usr/bin/true version on disk.
but the core file has the buildid in it (usually)....
next prev parent reply other threads:[~2020-02-07 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 17:33 Frank Ch. Eigler
2020-02-05 19:11 ` Arjan van de Ven
2020-02-05 19:14 ` Frank Ch. Eigler
2020-02-05 22:05 ` Arjan van de Ven
2020-02-07 9:13 ` Mark Wielaard
2020-02-07 14:47 ` Arjan van de Ven [this message]
2020-02-07 23:47 ` Mark Wielaard
2020-02-09 17:43 ` Arjan van de Ven
2020-02-07 9:06 ` Mark Wielaard
2020-02-07 14:46 ` Arjan van de Ven
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=ae41db4d-fe4f-152f-6ebc-d17921e49eae@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.com \
--cc=mark@klomp.org \
--cc=patrick.mccarty@intel.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).