This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tapsets/18598] New: staprun markers don't exist


https://sourceware.org/bugzilla/show_bug.cgi?id=18598

            Bug ID: 18598
           Summary: staprun markers don't exist
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com
  Target Milestone: ---

While working on bug #18577 and going through the semantic errors that 'stap
-vv -l **' produces, I noticed that I was getting errors from the
stap_staticmarkers.stp tapset. This tapset provides probe aliases for markers
built into stap and staprun.

Markers exist in stap:

====
# stap -l 'process("stap").mark("*")'
process("/usr/local/bin/stap").mark("benchmark")
process("/usr/local/bin/stap").mark("benchmark__end")
process("/usr/local/bin/stap").mark("benchmark__start")
process("/usr/local/bin/stap").mark("benchmark__thread__end")
process("/usr/local/bin/stap").mark("benchmark__thread__start")
process("/usr/local/bin/stap").mark("cache__add__module")
process("/usr/local/bin/stap").mark("cache__add__source")
process("/usr/local/bin/stap").mark("cache__clean")
process("/usr/local/bin/stap").mark("cache__get")
process("/usr/local/bin/stap").mark("client__end")
process("/usr/local/bin/stap").mark("client__start")
process("/usr/local/bin/stap").mark("pass0__end")
process("/usr/local/bin/stap").mark("pass0__start")
process("/usr/local/bin/stap").mark("pass1__end")
process("/usr/local/bin/stap").mark("pass1a__start")
process("/usr/local/bin/stap").mark("pass1b__start")
process("/usr/local/bin/stap").mark("pass2__end")
process("/usr/local/bin/stap").mark("pass2__start")
process("/usr/local/bin/stap").mark("pass3__end")
process("/usr/local/bin/stap").mark("pass3__start")
process("/usr/local/bin/stap").mark("pass4__end")
process("/usr/local/bin/stap").mark("pass4__start")
process("/usr/local/bin/stap").mark("pass5__end")
process("/usr/local/bin/stap").mark("pass5__start")
process("/usr/local/bin/stap").mark("pass6__end")
process("/usr/local/bin/stap").mark("pass6__start")
process("/usr/local/bin/stap").mark("stap_system__complete")
process("/usr/local/bin/stap").mark("stap_system__spawn")
process("/usr/local/bin/stap").mark("stap_system__start")
====

But, no markers can be found in staprun:

====
# stap -l 'process("staprun").mark("*")'
====

This is odd because several markers appear in the staprun source. Perhaps we've
got a build problem.

Note that the stap_staticmarkers.stp needs a buildok test case so that this
sort of problem would have been found sooner.

-- 
You are receiving this mail because:
You are the assignee for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]