From: Jiri Slaby <jirislaby@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: "Érico Rolim" <erico.erc@gmail.com>,
dwarves@vger.kernel.org, linux-kernel@vger.kernel.org,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Hao Luo" <haoluo@google.com>, "Andrii Nakryiko" <andriin@fb.com>
Subject: Re: Segfault in pahole 1.18 when building kernel 5.9.1 for arm64
Date: Wed, 21 Oct 2020 08:22:40 +0200 [thread overview]
Message-ID: <f7246cb6-901e-0bc3-eb18-194d1754da53@kernel.org> (raw)
In-Reply-To: <20201020122015.GH2294271@kernel.org>
On 20. 10. 20, 14:20, Arnaldo Carvalho de Melo wrote:
>> Yeah, I observe the very same. I reported it at:
>> https://bugzilla.suse.com/show_bug.cgi?id=1177921
>
> Would it be possible to try with
> https://git.kernel.org/pub/scm/devel/pahole/pahole.git/commit/?h=tmp.libbtf_encoder
> ?
Yes, that branch fixes the crashes and the kernel build finishes. The
zero-sized symbol error remains.
So what should distributions do now -- should we switch to a pahole
snapshot for a while?
thanks,
--
js
next prev parent reply other threads:[~2020-10-21 6:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 23:18 Segfault in pahole 1.18 when building kernel 5.9.1 for arm64 Érico Rolim
2020-10-20 9:01 ` Jiri Slaby
2020-10-20 12:20 ` Arnaldo Carvalho de Melo
2020-10-20 17:04 ` Hao Luo
2020-10-20 17:10 ` Andrii Nakryiko
2020-10-20 17:18 ` Hao Luo
2020-10-20 18:14 ` Arnaldo Carvalho de Melo
2020-10-20 19:02 ` Arnaldo Carvalho de Melo
2020-10-21 6:22 ` Jiri Slaby [this message]
2020-10-21 11:29 ` Arnaldo Carvalho de Melo
2020-10-21 15:53 ` Andrii Nakryiko
2020-10-21 16:26 ` Arnaldo Carvalho de Melo
2020-10-20 17:15 ` Andrii Nakryiko
2020-10-21 5:52 ` Jiri Slaby
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=f7246cb6-901e-0bc3-eb18-194d1754da53@kernel.org \
--to=jirislaby@kernel.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=andriin@fb.com \
--cc=dwarves@vger.kernel.org \
--cc=erico.erc@gmail.com \
--cc=haoluo@google.com \
--cc=linux-kernel@vger.kernel.org \
/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).