[Bug translator/2422] New: running multiple systemtap instrumentation when module("*") is used

["wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>]

If an existing systemtap probe is running, it has a module stap_[0-9]+ installed
in the kernel. When a second systemtap instrumentation probe is attempted the
translator cannot find debuginformation for the stap_[0-9]+ module. So for
example  the tests/testsuite/systemtap.stress/current.stp script was built and
left running (any systemtap instrumentation script would work). A second
current.stp script was attempted and failed in the following way:

$  stap -g  systemtap.stress/current.stp
semantic error: c$  stap -g  systemtap.stress/current.stp
semantic error: cannot find module stap_21942 debuginfo: No such file or directory
semantic error: cannot find module stap_21942 debuginfo: No such file or directory
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.
annot find module stap_21942 debuginfo: No such file or directory
semantic error: cannot find module stap_21942 debuginfo: No such file or directory
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.


This is also going to present a problem for any module that doesn't have
debugging information, e.g. third party device drivers. Shouldn't this be a
warning and just not instrument the module missing the debuginfo rather than
failing?

-- 
           Summary: running multiple systemtap instrumentation when
                    module("*") is used
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: wcohen at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=2422

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