Viktor Malík
Viktor Malík
What we could do here is emit subprograms into special sections named e.g. `.text.` and then transform the relevant section into `.text` for the given probe in `BpfProgram`. That should...
> > e.g. .text. and then transform the relevant section into .text for the given probe in BpfProgram. > > QQ: should it be probe id? I think you can...
Damn, yeah, I forgot that we're loading the created ELF with libbpf now: https://github.com/bpftrace/bpftrace/blob/master/src/bpfbytecode.cpp#L15 This may be quite tricky to do, I'm wondering if it is possible to tell libbpf...
> Is there anything I can do to help unblock libbpf-based loading? Not at the moment. It's a lot of work since we need to significantly rework the way we...
> if you are using libbpf to load ELF file This is currently WIP but it will take some time to land so we wanted to workaround this issue in...
Both would, many thanks! I'm slightly in favor of option 1, @jordalgo do you still have time to look at implementing this? Thanks!
Is the error happening on `bpf_object__open_mem`?
Ah sorry, I see the answer in one of your previous comments. It looks like we cannot resolve this in another way that moving to libbpf loading. Good news is...
Dropping the 0.21 milestone from this one as #3233 introduces a user-friendly error and the issue should get resolved by moving to libbpf-based loading.
I like the `for (item : range)` syntax, it's common in many languages, so I'd stick to that. > Tuple-destructuring (not needed right away): > ``` > @x[1,2] = 3;...