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 translator/6826] New: shorthand or variable for probed executable's path


Suppose the program I'm probing has a really long pathname, or at least one that
I'd rather not retype or copy&paste a lot.  Is there some way to arrange it so
every probe definition doesn't have to start with
  probe process("/a/really/long/pathname").whatever ...
?

BTW, I don't consider this a viable solution:
  probe process(@1).whatever ...
  stap xxx.stp /a/really/long/pathname

-- 
           Summary: shorthand or variable for probed executable's path
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: jkenisto at us dot ibm dot com


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

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


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