All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: dwarves@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	bpf@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
	Jan Engelhardt <jengelh@inai.de>,
	Domenico Andreoli <domenico.andreoli@linux.com>,
	Matthias Schwarzott <zzam@gentoo.org>, Yonghong Song <yhs@fb.com>,
	Douglas RAILLARD <douglas.raillard@arm.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>,
	Matteo Croce <mcroce@microsoft.com>
Subject: Re: ANNOUNCE: pahole v1.23 (BTF tags and alignment inference)
Date: Wed, 15 Dec 2021 11:56:19 -0300	[thread overview]
Message-ID: <YboCE3zig9papNQW@kernel.org> (raw)
In-Reply-To: <YbkTAPn3EEu6BUYR@archlinux-ax161>

Em Tue, Dec 14, 2021 at 02:56:16PM -0700, Nathan Chancellor escreveu:
> Hi Arnaldo,
> 
> On Wed, Dec 08, 2021 at 10:54:56AM -0300, Arnaldo Carvalho de Melo wrote:
> > - Initial support for DW_TAG_skeleton_unit, so far just suggest looking up a
> >   matching .dwo file to be used instead. Automagically doing this is in the
> >   plans for a future release.
> 
> This change [1] appears to break building on older distributions for me,
> which I use in containers for access to older versions of GCC. I see the
> error with Debian Stretch and Ubuntu Xenial, which have an older
> libelf-dev.  Is this expected? I don't mind sticking with 1.22 for
> those, I just want to be sure!

Nope, not expected, I'll reproduce here, fix and push, thanks for the
report.

- Arnaldo
 
> /tmp/dwarves-1.23/dwarf_loader.c: In function 'die__process':
> /tmp/dwarves-1.23/dwarf_loader.c:2529:13: error: 'DW_TAG_skeleton_unit' undeclared (first use in this function)
>   if (tag == DW_TAG_skeleton_unit) {
>              ^
> 
> [1]: https://git.kernel.org/pub/scm/devel/pahole/pahole.git/commit/?id=0135ccd632796ab3aff65b7c99b374c4682c2bcf
> 
> Cheers,
> Nathan

-- 

- Arnaldo

  reply	other threads:[~2021-12-15 14:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 21:25 ANNOUNCE: pahole v1.22 (Multithreaded DWARF Loading, detached BTF encoding) Arnaldo Carvalho de Melo
2021-08-23 21:55 ` Arnaldo Carvalho de Melo
2021-12-08 13:54 ` ANNOUNCE: pahole v1.23 (BTF tags and alignment inference) Arnaldo Carvalho de Melo
2024-02-28 19:39   ` ANNOUNCE: pahole v1.26 (more holes, --bpf_features, --contains_enum) Arnaldo Carvalho de Melo
2021-12-08 14:26   ` ANNOUNCE: pahole v1.23 (BTF tags and alignment inference) Jan Engelhardt
2021-12-08 18:35     ` Arnaldo Carvalho de Melo
2021-12-08 18:37       ` Arnaldo Carvalho de Melo
2021-12-08 18:49         ` Andrii Nakryiko
2021-12-08 19:11       ` Jan Engelhardt
2021-12-09 22:09         ` Yonghong Song
2021-12-12 10:03           ` Jan Engelhardt
2021-12-14 21:56   ` Nathan Chancellor
2021-12-15 14:56     ` Arnaldo Carvalho de Melo [this message]
2021-12-17 19:12     ` Arnaldo Carvalho de Melo
2024-05-16  9:36   ` ANNOUNCE: pahole v1.26 (more holes, --bpf_features, --contains_enum) Domenico Andreoli

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=YboCE3zig9papNQW@kernel.org \
    --to=acme@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=domenico.andreoli@linux.com \
    --cc=douglas.raillard@arm.com \
    --cc=dwarves@vger.kernel.org \
    --cc=iii@linux.ibm.com \
    --cc=jengelh@inai.de \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcroce@microsoft.com \
    --cc=nathan@kernel.org \
    --cc=yhs@fb.com \
    --cc=zzam@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.