bcc: bcc does not pick the right libraries
bcc is not considering the encoded hwcap when choosing libraries. As such, uprobes on a shared library does not work on powerpc, as seen with the uprobes test:
======================================================================
FAIL: test_simple_library (__main__.TestUprobes)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/root/bcc/tests/python/test_uprobes.py", line 34, in test_simple_library
self.assertEqual(b["stats"][ctypes.c_int(0)].value, 2)
AssertionError: 0L != 2
----------------------------------------------------------------------
libc libraries in cache:
# ldconfig -p | grep libc.so
libc.so.6 (libc6,64bit, hwcap: 0x0000200000000000, OS ABI: Linux 2.6.32) => /lib64/power8/libc.so.6
libc.so.6 (libc6,64bit, OS ABI: Linux 2.6.32) => /lib64/libc.so.6
bcc always picks the first library here, which won’t work on non-power8 machines.
We need to either implement stricter checks (look at hwcap and perhaps the platform) or consider probing on all libraries with the same name.
About this issue
- Original URL
- State: closed
- Created 11 years ago
- Reactions: 5
- Comments: 17 (8 by maintainers)
@pchaigno, Nice work on #875.
I just patched
tests/python/test_uprobes.pyto take advantage of it and got those tests to pass. I’ll submit a pull request with that, and a few other things soon…Sure. It looks like @vmg wrote much of this code. @vmg do you have ideas on how best to address this?
Not sure I understand the full issue or suggestion here. As it is now, we’re just using standard gcc logic when compiling.
If you run
make VERBOSE=1, can you capture the line where libbcc.so is linked, and make some modifications that cause it to work for you? If you could for instance identify a problematic gcc line, we could help in working that into the build definitions.