RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 820320 - WARNING: tapset '/usr/share/systemtap/tapset/qemu-kvm.stp' has errors
Summary: WARNING: tapset '/usr/share/systemtap/tapset/qemu-kvm.stp' has errors
Keywords:
Status: CLOSED DUPLICATE of bug 798676
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Asias He
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-09 15:42 UTC by Eric Sandeen
Modified: 2013-11-01 00:04 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-16 05:37:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Eric Sandeen 2012-05-09 15:42:30 UTC
When running systemtap with qemu-qvm installed, I get:

# stap -e 'probe vfs.read {exit()}'
parse error: expected literal string or number
	saw: operator '=' at /usr/share/systemtap/tapset/qemu-kvm.stp:814:8
     source:   next = $arg1;
                    ^
1 parse error.
WARNING: tapset '/usr/share/systemtap/tapset/qemu-kvm.stp' has errors, and will be skipped.


fche says:

[10:38]  <fche> next is a keyword in stap language

Comment 2 Frank Ch. Eigler 2012-05-09 15:44:00 UTC
The list of keywords to avoid is: 

probe, global, function, if, else, for, foreach, in, limit, return, delete, while, break, continue, next, string, long, try, catch

Comment 3 juzhang 2012-05-10 08:56:48 UTC
Hi,Eric

Please use the qemu-kvm>=qemu-kvm-0.12.1.2-2.287.el6 and have a try,thanks
FYI
Bug 798676 - do not use next as a variable name in qemu-kvm systemtap tapset(verified)

Comment 5 RHEL Program Management 2012-07-10 08:51:43 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 6 RHEL Program Management 2012-07-11 02:07:23 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 7 Ronen Hod 2012-07-16 05:37:33 UTC

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


Note You need to log in before you can comment on or make changes to this bug.