public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mrlong336 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/25794] New: stap command support to input multi stp scripts and parameters
Date: Mon, 06 Apr 2020 17:24:15 +0000	[thread overview]
Message-ID: <bug-25794-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 25794
           Summary: stap command support to input multi stp scripts and
                    parameters
           Product: systemtap
           Version: unspecified
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: mrlong336 at gmail dot com
  Target Milestone: ---

Requirement:
For example,there are four stp scripts, x1.stp x2.stp x3.stp x4.stp
1. I want to control them in shell script combining different script, such as
#stap x1.stp -c ./a.out
stap x1.stp x2.stp -c ./a.out
#stap x3.stp x4.stp -c ./a.out

Some solutions but not cool.
- something like -E, but it is so weak.
- "stap x.stp &" is not cool and can't use -c, I just want to run the program
once.

I think this usage should be developed firstly since systemtap was created.

2. I can pass different parameters into different scrip
stap -filelist x1.stp x2.stp -parameter p1 p2 -filelist x3.stp x4.stp
-parameter p3 p4 -c ./a.out
It will pass p1 and p2 into x1.stp and x2.stp, p3 and p3 into x3.stp and
x4.stp.

If a conflict found, then break down the program like c++ namespace conflict.

further, simple to write as:
stap -filelist x1.stp x2.stp p1 p2 x3.stp x4.stp p3 p4 -c ./a.out

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

             reply	other threads:[~2020-04-06 17:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 17:24 mrlong336 at gmail dot com [this message]
2020-04-06 17:34 ` [Bug translator/25794] " fche at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-25794-6586@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).