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
In our (Yocto) project we enabled the bcc & bpftrace tools. But the bcc selftest shows a few failures. During analysis we've a few observations as below.
We've tested the bcc tool with the generated binary 'test_libbcc_no_libbpf'. Also, I did bcc source code compilation on Ubuntu host machine but there 'test_libbcc' binary is generated (This binary has some extra tests Passed when compared to test_libbcc_no_libbpf binary) . Can anyone help me on below queries -
What configuration generates the different binaries 'test_libbcc' & 'test_libbcc_no_libbpf' binary generation.
There are certain config's ENABLE_USDT, ENABLE_TESTS ... etc are there in 'CMakeLists.txt' file. Where to enable/disable these config's for build? (or the 'CMakeLists.txt' will be considered for configurations?)
Is there any specific config to be enabled for failed tests (listed below)
We've below failures on arm64 machine with 'test_libbcc_no_libbpf':
FAIL: cc resolve symbol name in external zipped library
FAIL: cc resolve symbol name via symfs
FAIL: cc resolve symbol name via buildid
FAIL: cc resolve symbol name via gnu_debuglink
FAIL: cc resolve symbol name via mini debug info
FAIL: cc resolve symbol addresses for a given PID
FAIL: cc resolve symbols using /tmp/perf-pid.map
FAIL: cc test bpf stack table
FAIL: cc test bpf stack_id table
FAIL: cc test hash of maps
FAIL: cc test hash of maps using custom key
FAIL: cc test array of maps
FAIL: cc test read perf event
FAIL: cc test usdt argument parsing
FAIL: cc test finding a probe in our own process
FAIL: cc test fine a probe in our own binary with C++ API
FAIL: cc test fine probes in our own binary with C++ API
FAIL: cc test fine a probe in our Process with C++ API
FAIL: cc test find a probe in our process' shared libs with c++ API
FAIL: cc test usdt partial init w/ fail init_usdt
FAIL: cc Test uprobe refcnt semaphore activation
FAIL: cc finds entries in a zip archive by name
FAIL: cc finds entries in a zip archive by offset
FAIL: cc open zip archive and finds an entry
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
In our (Yocto) project we enabled the bcc & bpftrace tools. But the bcc selftest shows a few failures. During analysis we've a few observations as below.
We've tested the bcc tool with the generated binary 'test_libbcc_no_libbpf'. Also, I did bcc source code compilation on Ubuntu host machine but there 'test_libbcc' binary is generated (This binary has some extra tests Passed when compared to test_libbcc_no_libbpf binary) . Can anyone help me on below queries -
We've below failures on arm64 machine with 'test_libbcc_no_libbpf':
Thanks,
Sundeep K.
Beta Was this translation helpful? Give feedback.
All reactions