[Bug bpf/24639] "next" statement not recognized by stap bpf backend
wcohen at redhat dot com
sourceware-bugzilla@sourceware.org
Thu Jun 6 21:30:00 GMT 2019
https://sourceware.org/bugzilla/show_bug.cgi?id=24639
--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
Created attachment 11817
--> https://sourceware.org/bugzilla/attachment.cgi?id=11817&action=edit
next.stp with diagnostic prints.
ignore the previous -e example. that isn't reproducing the problem.
It looks like changes in the values made by the kernel.function("vfs_read")
probes are not seen in the probe end. Put in the diagnostic printf in the
probes to better see what is going on.
[wcohen@localhost systemtap]$ ../install/bin/stap --bpf next.stp
BEGIN
vfs_read
value 2
status 0
end
value 2
status 2
END FAIL
[wcohen@localhost systemtap]$ ../install/bin/stap --bpf next.stp
BEGIN
vfs_read
value 0
status 0
end
value 2
status 2
END FAIL
--- Comment #4 from William Cohen <wcohen at redhat dot com> ---
Created attachment 11818
--> https://sourceware.org/bugzilla/attachment.cgi?id=11818&action=edit
next.stp with diagnostic prints.
ignore the previous -e example. that isn't reproducing the problem.
It looks like changes in the values made by the kernel.function("vfs_read")
probes are not seen in the probe end. Put in the diagnostic printf in the
probes to better see what is going on.
[wcohen@localhost systemtap]$ ../install/bin/stap --bpf next.stp
BEGIN
vfs_read
value 2
status 0
end
value 2
status 2
END FAIL
[wcohen@localhost systemtap]$ ../install/bin/stap --bpf next.stp
BEGIN
vfs_read
value 0
status 0
end
value 2
status 2
END FAIL
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Systemtap
mailing list