Description of problem: The qemu-user and qemu-system-* subpackage includes a number of systemtap tapset definitions that get installed into /usr/share/systemtap/tapset. Every one of these tapset definitions fails to compile because they use systemtap language reserved words as variables (specifically: in, next). This lots of error messages whenever a systemtap script is compiled. Version-Release number of selected component (if applicable): rpm -qa qemu-user qemu-system\* qemu-system-x86-1.0-17.fc17.x86_64 qemu-system-m68k-1.0-17.fc17.x86_64 qemu-system-sh4-1.0-17.fc17.x86_64 qemu-user-1.0-17.fc17.x86_64 qemu-system-arm-1.0-17.fc17.x86_64 qemu-system-cris-1.0-17.fc17.x86_64 qemu-system-mips-1.0-17.fc17.x86_64 How reproducible: always Steps to Reproduce: 1. Write the simplest systemtap script possible: $ cat hello-world.stp probe begin { print ("hello world\n") exit () } 2. Try to compile the systemtap script: $ stap hello-world.stp Actual results: $ stap hello-world.stp parse error: expected statement saw: keyword at /usr/share/systemtap/tapset/qemu-alpha.stp:1139:3 source: in = $arg3; ^ parse error: expected literal string or number saw: operator '=' at /usr/share/systemtap/tapset/qemu-alpha.stp:2078:8 source: next = $arg1; ^ 2 parse errors. WARNING: tapset '/usr/share/systemtap/tapset/qemu-alpha.stp' has errors, and will be skipped. [... Same set of parse errors at the same line numbers for each tapset file that is packaged ...] Expected results: $ stap hello-world.stp hello world Additional info:
Fixed in upstream QEMU, but hasn't made it into Fedora's QEMU yet commit 256a721d46a112d8807a488ec0176985c09bbbf1 Author: Stefan Hajnoczi <stefanha.ibm.com> Date: Mon Apr 16 12:47:58 2012 +0100 tracetool: handle DTrace keywords 'in', 'next', 'self' Language keywords cannot be used as argument names. The DTrace backend appends an underscore to the argument name in order to make the argument name legal. This patch adds 'in', 'next', and 'self' keywords to dtrace.py. Also drop the unnecessary argument name lstrip() call. The Arguments.build() method already ensures there is no space around argument names. Furthermore it is misleading to do the lstrip() *after* checking against keywords because the keyword check would not match if spaces were in the name. Signed-off-by: Stefan Hajnoczi <stefanha.ibm.com> Reviewed-by: Alon Levy <alevy> Reviewed-by: Lluís Vilanova <vilanova.edu>
*** Bug 811749 has been marked as a duplicate of this bug. ***
*** Bug 821186 has been marked as a duplicate of this bug. ***
*** Bug 829102 has been marked as a duplicate of this bug. ***
qemu-0.15.1-7.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/qemu-0.15.1-7.fc16
qemu-1.0.1-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/qemu-1.0.1-1.fc17
Package qemu-1.0.1-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing qemu-1.0.1-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11302/qemu-1.0.1-1.fc17 then log in and leave karma (feedback).
qemu-0.15.1-7.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
qemu-1.0.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.