From: Arnaldo <arnaldo.melo@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
dwarves@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Kernel Team <kernel-team@fb.com>, Roman Gushchin <guro@fb.com>
Subject: Re: pahole and libdwarves linking/versioning issues
Date: Tue, 10 Nov 2020 21:28:15 -0300 [thread overview]
Message-ID: <34B5347B-DCF8-479E-B638-204D90A2910A@gmail.com> (raw)
In-Reply-To: <CAEf4BzYc6sHzGW-mmHSaTgG4zOc8S9Dxegnufbc+myr7wTmRcw@mail.gmail.com>
On November 10, 2020 9:14:16 PM GMT-03:00, Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
>Hey Arnaldo,
>
>We use pahole pretty extensively here at Facebook, as you might
>imagine, given it's a required tool to compile Linux kernel with BTF.
>
>There are a few problems we periodically run into, all of which seems
>to be related to the fact that pahole is just a thin wrapper binary on
>top of libdwarves shared library.
>
>One very common problem is when we upgrade the dwarves package from
>one minor version to another one. Typically people would do
>
>yum upgrade dwarves
I'll reply to this more thoroughly tomorrow morning.
But yes, the spec file um the pahole git repo has a explicit Requires: tag to ask for the latest libdwarves.
- Arnaldo
>
>And that would succeed to update the dwarves package (say 1.13 to
>1.16). But when you run
>
>pahole --version
>
>You'll still see 1.13 (and still have 1.13 functionality, of
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2020-11-11 0:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 0:14 pahole and libdwarves linking/versioning issues Andrii Nakryiko
2020-11-11 0:28 ` Arnaldo [this message]
2020-11-13 11:45 ` Arnaldo Carvalho de Melo
2020-12-04 23:11 ` Andrii Nakryiko
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=34B5347B-DCF8-479E-B638-204D90A2910A@gmail.com \
--to=arnaldo.melo@gmail.com \
--cc=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=guro@fb.com \
--cc=kernel-team@fb.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 NNTP newsgroup(s).