Description of problem: bpftrace errors out with `Unrecognized probe type` Version-Release number of selected component (if applicable): bpftrace-0.14.0-2.fc36 How reproducible: reliably Steps to Reproduce: a. bpftrace -e 'uprobe:libc:malloc { }' b. bpftrace -e 'usdt:/my/app:probe_name { }' Actual results: a. stdin:1:1-19: ERROR: Unrecognized probe type: uprobe b. stdin:1:1-24: ERROR: Unrecognized probe type: usdt Expected results: bpftrace traces probes
This is broken for me as well, on all my fedora 36 hosts. Looks like the previous package (bpftrace-0.14.0-1.fc36) works as expected.
Any insight on this from the fedora maintainers? Even though there is a straightforward workaround (downgrade to an older version), seems unfortunate to release fedora 36 with an unusable bpftrace. As a developer who often works on kernel code, it's a pretty important part of my workflow. Maybe it should be reported upstream, but I don't know if the breakage is specific to Fedora.
(In reply to Marc Dionne from comment #2) > Any insight on this from the fedora maintainers? > > Even though there is a straightforward workaround (downgrade to an older > version), seems unfortunate to release fedora 36 with an unusable bpftrace. > As a developer who often works on kernel code, it's a pretty important part > of my workflow. Maybe it should be reported upstream, but I don't know if > the breakage is specific to Fedora. I'm investigating the problem...
(In reply to Marc Dionne from comment #2) > Any insight on this from the fedora maintainers? > > Even though there is a straightforward workaround (downgrade to an older > version), seems unfortunate to release fedora 36 with an unusable bpftrace. > As a developer who often works on kernel code, it's a pretty important part > of my workflow. Maybe it should be reported upstream, but I don't know if > the breakage is specific to Fedora. Could you try out the following build and give me a feedback? https://koji.fedoraproject.org/koji/taskinfo?taskID=86534893 https://kojipkgs.fedoraproject.org//work/tasks/4948/86534948/bpftrace-0.14.1-1.fc36.x86_64.rpm
(In reply to Augusto Caringi from comment #4) > (In reply to Marc Dionne from comment #2) > > Any insight on this from the fedora maintainers? > > > > Even though there is a straightforward workaround (downgrade to an older > > version), seems unfortunate to release fedora 36 with an unusable bpftrace. > > As a developer who often works on kernel code, it's a pretty important part > > of my workflow. Maybe it should be reported upstream, but I don't know if > > the breakage is specific to Fedora. > > Could you try out the following build and give me a feedback? > > https://koji.fedoraproject.org/koji/taskinfo?taskID=86534893 > > https://kojipkgs.fedoraproject.org//work/tasks/4948/86534948/bpftrace-0.14.1- > 1.fc36.x86_64.rpm That package works fine for me, at least for the few examples I tried.
FEDORA-2022-c4da511bbe has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c4da511bbe
FEDORA-2022-c4da511bbe has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-c4da511bbe` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c4da511bbe See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-c4da511bbe has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.