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
Just ran into this issue while building / testing on Debian 8 amd64.
mikep@mv-tricolor:~/bcc/obj-x86_64-linux-gnu$ sudo /usr/bin/ctest --force-new-ctest-process -j1 -V
...
20: Test command: /home/mikep/bcc/obj-x86_64-linux-gnu/tests/wrapper.sh "py_uprobes" "sudo" "/home/mikep/bcc/tests/python/test_uprobes.py"
20: Test timeout computed to be: 9.99988e+06
20: Python 2.7.9
20: .Arena 0:
20: system bytes = 13799424
20: in use bytes = 2969696
20: Total (incl. mmap):
20: system bytes = 14589952
20: in use bytes = 3760224
20: max mmap regions = 4
20: max mmap bytes = 1589248
20: F
20: ======================================================================
20: FAIL: test_simple_library (__main__.TestUprobes)
20: ----------------------------------------------------------------------
20: Traceback (most recent call last):
20: File "/home/mikep/bcc/tests/python/test_uprobes.py", line 34, in test_simple_library
20: self.assertEqual(b["stats"][ctypes.c_int(0)].value, 2)
20: AssertionError: 0L != 2
20:
20: ----------------------------------------------------------------------
20: Ran 2 tests in 0.217s
20:
20: FAILED (failures=1)
20: Failed
20/28 Test #20: py_uprobes .......................***Failed 0.29 sec
Looks like malloc_stats() is missing from this distro and version.
mikep@mv-tricolor:~$ python
Python 2.7.9 (default, Jun 29 2016, 13:08:31)
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from ctypes.util import find_library
>>> find_library('malloc_stats')
>>> find_library('c')
'libc.so.6'
@rnav, would you mind doing the same check with python and find_library() on the host where you discovered this issue?
Looks like
malloc_stats()
is missing from this distro and version.@rnav, would you mind doing the same check with python and
find_library()
on the host where you discovered this issue?Originally posted by @mprzybylski in #525 (comment)
The text was updated successfully, but these errors were encountered: