While working on #1728 I found that some APIs changed since the last release. We should probably cut another release to allow people to hack on tools easily.
Examples of errors I'm facing:
Traceback (most recent call last):
File "/tmp/runqslower.py", line 213, in <module>
is_support_raw_tp = BPF.support_raw_tracepoint()
AttributeError: type object 'BPF' has no attribute 'support_raw_tracepoint'
Traceback (most recent call last):
File "/tmp/runqslower.py", line 261, in <module>
b.perf_buffer_poll()
AttributeError: 'BPF' object has no attribute 'perf_buffer_poll'
cc @yonghong-song, @drzaeus77, @palmtenor
@brendangregg
To add to the list, here is a error that I'm seeing:
```root@test2:~/bcc/examples/tracing# ./trace_fields.py
Traceback (most recent call last):
File "./trace_fields.py", line 19, in
b.attach_kprobe(event=b.get_syscall_fnname("clone"), fn_name="hello")
AttributeError: 'BPF' object has no attribute 'get_syscall_fnname'
root@test2:~/bcc/examples/tracing# ./trace_perf_output.py
Traceback (most recent call last):
File "./trace_perf_output.py", line 43, in
event_name = b.get_syscall_fnname("clone")
AttributeError: 'BPF' object has no attribute 'get_syscall_fnname'
root@test2:~/bcc/examples/tracing# ./hello_perf_output.py
Traceback (most recent call last):
File "./hello_perf_output.py", line 35, in
b.attach_kprobe(event=b.get_syscall_fnname("clone"), fn_name="hello")
AttributeError: 'BPF' object has no attribute 'get_syscall_fnname'
```
Just wanted kindly to check is there any sort of rough estimate for the release date of the next release yet? There seems to be some Python 3 fixes in the master since 0.5.0 as well so a new release would be nice in that sense as well. Thanks.
I'm hoping to enable a Fedora 28 buildbot in the next day or two, and will tag a release after that. Hopefully by the end of the week.
This is wonderful news, thanks for letting us know!
Hi, just to update, I've fixed a few of the Fedora 28 issues and am working on the last one, so the tag hasn't been created yet but shouldn't be much longer.
@drzaeus77 Just wandering what is the progress on the new release? Any help you need?
v0.6.0 is tagged and packages published. Unfortunately, fedora 28 support is not included.
Apt packages seem to only have 0.5.0 in the index:
$ curl -s https://repo.iovisor.org/apt/xenial/dists/xenial/main/binary-amd64/Packages | grep ^Version
Version: 0.5.0-1
Version: 0.5.0-1
Version: 0.5.0-1
Version: 0.5.0-1
Version: 0.5.0-1
Actual deb files are there, it's just index that is out of date:

Can you regenerate the index?
cc @drzaeus77
It is updated now.
Thanks!
On Fedora 28, I still see error like AttributeError: 'BPF' object has no attribute 'get_syscall_fnname' Fixes not yet available F28?
Is that because https://repo.iovisor.org/yum/{nightly|main}/ doesn't have a f28 subfolder yet?
Hit below error on ubuntu 18.04 which isn't hit on ubuntu 16.04:
'BPF' object has no attribute 'get_syscall_fnname'
On ubuntu 18.04, I find that bcc version is 0.5.0
On ubuntu 16.04, bcc module version is 0.6.0
However, I failed to install 0.6.0 bcc python module with below command on ubuntu 18.04. Any suggestion?
sudo pip install --force-reinstall bcc==0.6.0
No matching distribution found for bcc==0.6.0
cc @drzaeus77
The 0.6.1 version is the latest, and only bionic supported version. The following should work for the tagged packages:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys D4284CDD
echo "deb https://repo.iovisor.org/apt/bionic bionic main" | sudo tee /etc/apt/sources.list.d/iovisor.list
sudo apt-get update
sudo apt-get install python-bcc
Most helpful comment
The 0.6.1 version is the latest, and only bionic supported version. The following should work for the tagged packages: