Bug 821186

Summary: tapset errors in qemu-kvm.stp with "in" and "from" keywords
Product: [Fedora] Fedora Reporter: Dominic Cleal <dcleal>
Component: qemuAssignee: Fedora Virtualization Maintainers <virt-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 17CC: amit.shah, berrange, cfergeau, crobinso, dwmw2, ehabkost, itamar, knoel, pbonzini, scottt.tw, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-10 07:23:33 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description Dominic Cleal 2012-05-12 18:02:37 EDT
Description of problem:
Trying to run an unrelated systemtap script shows two parse errors with these lines:

in = $arg3;
next = $arg1;

Identical errors are shown for qemu-kvm.stp, qemu-system-i386.stp and qemu-system-x86_64.stp, showing a total of six.

Version-Release number of selected component (if applicable):
qemu-system-x86-1.0-17.fc17.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. run stap -e ''
2. check for any parse errors relating to qemu
  
Actual results:
$ stap -e ''
Input file '<input>' is empty or missing.
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.


Expected results:
$ stap -e ''
Input file '<input>' is empty or missing.

Additional info:
Already reported against RHEL 6 as bug #720979, bug #798676 and #820320.  These only report the "next" error, not the "in" error though.

See bug #820320, comment #2 for a list of all reserved keywords.
Comment 1 Cole Robinson 2012-07-10 07:23:33 EDT

*** This bug has been marked as a duplicate of bug 831763 ***