public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/15942] New: support abbreviated process.* probes with stap -x PID
Date: Tue, 10 Sep 2013 20:26:00 -0000	[thread overview]
Message-ID: <bug-15942-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 15942
           Summary: support abbreviated process.* probes with stap -x PID
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: fche at redhat dot com

PR12427 introduced the ability to let a user abbreviate process
probes by inferring the path from the -c CMD argument.  We can do
the same with -x PID, perhaps the following way:

- stap --no-use-server -e 'probe process.foo {}' -x PID
  .... map to process("PATH") where PATH = readlink("/proc/PID/exe"),
  in the same place as PR12427 (dwarf_builder::build)

- stap --use-server -e 'probe process.foo {}' -x PID
  .... map to stap server_options "-c PATH" with same PATH
  (IOW, pretend to the stap-server that the user typed -c PATH).

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

             reply	other threads:[~2013-09-10 20:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 20:26 fche at redhat dot com [this message]
2014-05-30 21:01 ` [Bug translator/15942] " ajakop 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-15942-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).