Control: tag -1 +pending On Sat, 2018-02-17 at 20:20 +0200, Mykola Nikishov wrote: > --8<---------------cut here---------------start------------->8--- > $ sudo pythonflow-bpfcc > /usr/sbin/pythonflow-bpfcc: line 3: /usr/sbin/lib/uflow: No such file > or directory > $ sudo javacalls-bpfcc > /usr/sbin/javacalls-bpfcc: line 3: /usr/sbin/lib/ucalls: No such file > or directory > --8<---------------cut here---------------end--------------->8--- > > ucalls is actually located in a quite strange location:
Thanks for the bug report. I have fixed the issue you reported in
particular. But bcc's installation locations are quite broken and I
have to keep fighting some of these choices.
For example, bcc still installs binaries in non-standard locations, and
their paths hard-coded in helper scripts.
rrs@priyasi:~/rrs-home/Community/Packaging/bpfcc (master)$ dpkg -L
bpfcc-tools | grep lib
/usr/sbin/lib
/usr/sbin/lib/ucalls
/usr/sbin/lib/uflow
/usr/sbin/lib/ugc
/usr/sbin/lib/uobjnew
/usr/sbin/lib/ustat
/usr/sbin/lib/uthreads
/usr/share/doc/bpfcc-tools/examples/doc/lib
/usr/share/doc/bpfcc-tools/examples/doc/lib/ucalls_example.txt
/usr/share/doc/bpfcc-tools/examples/doc/lib/uflow_example.txt.gz
/usr/share/doc/bpfcc-tools/examples/doc/lib/ugc_example.txt
/usr/share/doc/bpfcc-tools/examples/doc/lib/uobjnew_example.txt
/usr/share/doc/bpfcc-tools/examples/doc/lib/ustat_example.txt
/usr/share/doc/bpfcc-tools/examples/doc/lib/uthreads_example.txt
13:54 ♒♒♒ ☺
Eventually, I'll fix those scripts to look for at a standard location.
Regarding your actual issue, it works now. But it'll need support from
runtime environments too, something that is beyond bcc's scope.
rrs@priyasi:~/rrs-home/Community/Packaging/bpfcc (master)$ sudo
pythonflow-bpfcc
usage: uflow [-h] [-l {java,python,ruby,php}] [-M METHOD] [-C CLAZZ] [-v] pid
uflow: error: too few arguments
13:55 ♒♒♒ ☹ => 2
rrs@priyasi:~/rrs-home/Community/Packaging/bpfcc (master)$ sudo
pythonflow-bpfcc -l python 25769
Error attaching USDT probes: the specified pid might not contain the
given language's runtime, or the runtime was not built with the required
USDT probes. Look for a configure flag similar to --with-dtrace or
--enable-dtrace. To check which probes are present in the process, use the
tplist tool.
13:55 ♒♒♒ ☹ => 1
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
