Red Hat Bugzilla – Bug 829102
qemu-supplied SystemTap tapsets cause errors
Last modified: 2013-01-09 07:03:03 EST
parse error: expected statement saw: keyword at /usr/share/systemtap/tapset/qemu-kvm.stp:1139:3 source: in = $arg3; ^ parse error: expected literal string or number saw: operator '=' at /usr/share/systemtap/tapset/qemu-kvm.stp:2078:8 source: next = $arg1; ^ 2 parse errors. parse error: expected statement saw: keyword at /usr/share/systemtap/tapset/qemu-system-i386.stp:1139:3 source: in = $arg3; ^ parse error: expected literal string or number saw: operator '=' at /usr/share/systemtap/tapset/qemu-system-i386.stp:2078:8 source: next = $arg1; ^ 2 parse errors. parse error: expected statement saw: keyword at /usr/share/systemtap/tapset/qemu-system-x86_64.stp:1139:3 source: in = $arg3; ^ parse error: expected literal string or number saw: operator '=' at /usr/share/systemtap/tapset/qemu-system-x86_64.stp:2078:8 source: next = $arg1; ^ 2 parse errors. "in" and "next" are both SystemTap keywords.
This has been fixed upstream already for "next", but "in" still remains and will still cause syntax errors. usb_host_req_data(int bus, int addr, void *p, int in, int ep, int size) "dev %d:%d, packet %p, in %d, ep %d, size %d" Gerd, can you look at this?
*** This bug has been marked as a duplicate of bug 831763 ***