Why am I getting parse and semantic errors while running systemtap script?

Solution Verified - Updated -

Issue

  • Getting parse errors while running the iostat-scsi systemtap script.
# stap /usr/share/doc/systemtap-client-1.8/examples/io/iostat-scsi.stp 10
parse error: embedded code in unprivileged script; need stap -g
        saw: embedded-code at /usr/share/doc/systemtap-client-1.8/examples/io/iostat-scsi.stp:28:1
     source: %{
             ^
parse error: embedded code in unprivileged script; need stap -g
        saw: embedded-code at /usr/share/doc/systemtap-client-1.8/examples/io/iostat-scsi.stp:32:39
     source: function get_nr_sectors:long(rq:long) %{ /* pure */
                                                   ^
2 parse errors.
Pass 1: parse failed.  Try again with another '--vp 1' option.
  • Semantic error while running stap script.
# stap -v --all-modules bt.stap
semantic error: missing x86_64 kernel/module debuginfo [man warning::debuginfo] under '/lib/modules/2.6.32-504.8.1.el6.x86_64/build'
semantic error: while resolving probe point: identifier 'kernel' at :13:7
        source: probe kernel.function("__sock_create").call
                      ^

semantic error: missing x86_64 kernel/module debuginfo [man warning::debuginfo] under '/lib/modules/2.6.32-504.8.1.el6.x86_64/build'

Environment

  • Red Hat Enterprise Linux 6
  • systemtap
  • kernel

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content