You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cilium has a nice feature in their link package where:
If attaching to symbol fails, automatically retries with the running platform's syscall prefix (e.g. _x64) to support attaching to syscalls in a portable fashion.
I'm opening this issue here since I was using bpfman on k8s and my Kprobeprogram couldn't be loaded successfully (I couldn't figure out the error messages, until I realized the error was the symbol I was trying to attach the kprobe to was missing the __x64_ prefix -- which I wasn't really paying to much attention to since I was using link.Kprobe). However, I'm not sure if this should go in the bfpman repo instead.
I don't know much Rust myself, but I might be able to put something together for this small convenience function (although, if there's a place where we can do this in Go I can probably help better!)
The text was updated successfully, but these errors were encountered:
Cilium has a nice feature in their
link
package where:It catches any
file not found
errors and then it usesinternal.PlatformPrefix
(from the internal package) to prepend the right prefix to the function symbol to then try again: https://github.com/cilium/ebpf/blob/v0.16.0/link/kprobe.go#L171C1-L176C3I'm opening this issue here since I was using bpfman on k8s and my
Kprobeprogram
couldn't be loaded successfully (I couldn't figure out the error messages, until I realized the error was the symbol I was trying to attach the kprobe to was missing the__x64_
prefix -- which I wasn't really paying to much attention to since I was usinglink.Kprobe
). However, I'm not sure if this should go in the bfpman repo instead.I don't know much Rust myself, but I might be able to put something together for this small convenience function (although, if there's a place where we can do this in Go I can probably help better!)
The text was updated successfully, but these errors were encountered: