Viktor Malík

> Nice change! > > There's just a test failure in `call.path_in_unsupported_fentry` and I think an extra test file needs deleting/renaming. Good catch! I wonder why the GHA run on...

Hi, thanks for the report! First, not all functions from `kallsyms` are traceable, the actual list is in `/sys/kernel/tracing/available_filter_functions`. Could you check if the function is there? The warning that...

> Hi thanks for your reply > > 1. I use bpftrace in android 14 devices with kernel 6.1, i can't find `/sys/kernel/tracing/available_filter_functions` > > ```shell > ls /sys/kernel/tracing/available_* >...

Ok, it seems that Android is missing some things which are normally available on Linux. Could you please run `bpftrace --info` so that we have a bit more context about...

You're using bpftrace version 0.17.1 which is over a year old. Could you please try a newer version, preferably the latest one built from master?

FWIW, I think that the same potential issue applies to BPF programs in general and we should follow whatever practice is used by BPF upstream to mitigate this (if there's...

This seems closely related to #1834. That one also suggest to use the `bpf_snprintf_btf` helper which produces practically the same output as your implementation here. In addition, it doesn't need...

> > This seems closely related to #1834. That one also suggest to use the bpf_snprintf_btf helper which produces practically the same output as your implementation here. In addition, it...

Having new `printf` format specifiers sounds good to me, although I'm not sure if it won't be confusing to users as they'd expect `printf` to have the "commonly known specifiers"...

@amiremohamadi I already started working on that and it turns out not to be that simple... Here's the discussion if you want to have a look: https://lore.kernel.org/bpf/[email protected]/T/#m56f5f074e2ad956b3e49855ec72a198ad1c496fa