We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hi whitehat, coredump on ubuntu 21.04, and what env you used ?
os:ubuntu 21.04 kernel: Linux vm-server 5.11.0-49-generic #55-Ubuntu SMP Wed Jan 12 17:36:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux golang:go version go1.17.2 linux/amd64 clang:Ubuntu clang version 12.0.0-3ubuntu1~21.04.2 libbpf:0.6.1/0.7.0
make sudo make install boopkit -x 127.0.0.1 -> Logs: cat /sys/kernel/tracing/trace_pipe -> Loading eBPF Probe: /root/.boopkit/pr0be.safe.o -> Obfuscating PID: 12973 -> eBPF Probe loaded: /root/.boopkit/pr0be.safe.o -> Loading eBPF Probe: /root/.boopkit/pr0be.boop.o libbpf: failed to find BTF for extern 'inet_ntop' [28] section: -2 Segmentation fault
why linker create two *UND* section into pr0be.boop.o for inet_ntop and inet_pton. how can it works?
*UND*
pr0be.boop.o
inet_ntop
inet_pton
thanks.
The text was updated successfully, but these errors were encountered:
CC @fkautz
Sorry, something went wrong.
Its an implicit reference to the glibc <arpa/inet.h> I believe. I can try to recreate and follow up with an answer.
<arpa/inet.h>
I pushed a commit that uses the autogenerated vmlinux.h instead of including libbpf and glibc directly.
vmlinux.h
328d4bf
You should be able to compile if you run from HEAD.
Please share if this does not work.
the bug is not fixed... still error with "libbpf: failed to find BTF for extern 'inet_ntop' [28] section: -2"
can you give your environment?
No branches or pull requests
hi whitehat, coredump on ubuntu 21.04, and what env you used ?
env
os:ubuntu 21.04
kernel: Linux vm-server 5.11.0-49-generic #55-Ubuntu SMP Wed Jan 12 17:36:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
golang:go version go1.17.2 linux/amd64
clang:Ubuntu clang version 12.0.0-3ubuntu1~21.04.2
libbpf:0.6.1/0.7.0
how to reproduce
debug with gdb
why
why linker create two
*UND*
section intopr0be.boop.o
forinet_ntop
andinet_pton
.how can it works?
thanks.
The text was updated successfully, but these errors were encountered: