summaryrefslogtreecommitdiffstats
path: root/dynamic-layers/selinux/android-tools
diff options
context:
space:
mode:
authorDaniel Thompson <daniel@redfelineninja.org.uk>2022-05-19 09:37:18 +0000
committerKhem Raj <raj.khem@gmail.com>2022-09-03 14:16:53 -0700
commit3d63d0fd6296e23c7cbbae431e20aa3985ec69dd (patch)
tree165619f657d2b0bb29353bd27a9492f5ab25b363 /dynamic-layers/selinux/android-tools
parent3ef1d5c79985263436b3a240ea06375cbef7fcf3 (diff)
downloadmeta-clang-3d63d0fd6296e23c7cbbae431e20aa3985ec69dd.tar.gz
bcc: De-vendor libbpf
Currently bcc builds against a vendored copy of libbpf. This causes problems for bpftrace which is built against bcc and the system libbpf. The resulting version skew between the vendored and system versions of libbpf resulting in a SEGV whenever bpftrace is used. Although --help and -l (list probe points) work OK that is because they do not actually use BPF! Anything that does use BPF will crash immediately, including bpftrace --info and simple one-liners such as: ~# bpftrace -e 't:raw_syscalls:sys_exit { printf("%s", comm); }' Attaching 1 probe... Segmentation fault Note that this issue is very closely related to similar problems compiling bpftrace against mixed headers from the two libbpf versions. Fixes: https://github.com/iovisor/bpftrace/issues/2173 Fixes: bb3e56b06f9d ("bpftrace: Fix build with new libbpf") Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
Diffstat (limited to 'dynamic-layers/selinux/android-tools')
0 files changed, 0 insertions, 0 deletions