From: Steven Rostedt <rostedt@goodmis.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: Build failure bft for trace-cmd and libtraceevent
Date: Sun, 8 Feb 2026 16:32:11 -0500 [thread overview]
Message-ID: <20260208163211.63e645cb@robin> (raw)
In-Reply-To: <5984db8a-a93a-4efc-9b81-c87140d38042@benettiengineering.com>
On Sun, 8 Feb 2026 21:53:31 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Otherwise the solution could be to switch according to Linux version
> between print_args() with and without bft support, basically re-adding
> the function here:
> https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/commit/?id=e798103c0815e6642e74d9317c325b2c62681f2e
>
> What do you think about it?
Is the failure found at runtime? That is, the loaded BTF file doesn't
parse correctly? What is the error exactly?
I guess if the tep_btf_print_args() fails, it should just print the raw
args then.
-- Steve
next prev parent reply other threads:[~2026-02-08 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-08 20:53 Build failure bft for trace-cmd and libtraceevent Giulio Benetti
2026-02-08 21:32 ` Steven Rostedt [this message]
2026-02-08 21:44 ` Giulio Benetti
2026-02-08 22:01 ` Steven Rostedt
2026-02-08 22:14 ` Giulio Benetti
2026-02-08 22:22 ` Steven Rostedt
2026-02-10 18:01 ` Giulio Benetti
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=20260208163211.63e645cb@robin \
--to=rostedt@goodmis.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=linux-trace-devel@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