public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/17352] New: probing by pid using --runtime=dyninst not having -x or -c set
Date: Fri, 05 Sep 2014 14:45:00 -0000	[thread overview]
Message-ID: <bug-17352-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 17352
           Summary: probing by pid using --runtime=dyninst not having -x
                    or -c set
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: mcermak at redhat dot com
                CC: ajakop at redhat dot com, jistone at redhat dot com

When probing by pid using the "probe process(<pid>)" syntax and not having -x
or -c specified, --runtime=dyninst mode complains about missing -x or -c switch
and does not actually work:

-------------------------------8<------------------------------------
 7.0 S x86_64 # cat test.c 
void nop() {};

int main() {
        while(!sleep(1)) nop();
        return(0);
}
 7.0 S x86_64 # gcc -g test.c 
 7.0 S x86_64 # ./a.out &
[3] 22364
 7.0 S x86_64 # stap -ve 'probe process(22364).function("nop") {log("hit")}'
Pass 1: parsed user script and 113 library script(s) using
218008virt/35320res/3048shr/32732data kb, in 160usr/10sys/164real ms.
Pass 2: analyzed script: 1 probe(s), 1 function(s), 0 embed(s), 0 global(s)
using 218800virt/36688res/3680shr/33524data kb, in 0usr/0sys/5real ms.
Pass 3: translated to C into
"/tmp/stapKiiPjT/stap_f9cb621ebc98e2e2c85401cabfef45cc_1093_src.c" using
219064virt/37288res/4072shr/33788data kb, in 10usr/40sys/57real ms.
Pass 4: compiled C into "stap_f9cb621ebc98e2e2c85401cabfef45cc_1093.ko" in
1860usr/250sys/2124real ms.
Pass 5: starting run.
hit
hit
hit
^CPass 5: run completed in 20usr/60sys/3249real ms.
 7.0 S x86_64 # stap --runtime=dyninst -ve 'probe
process(22364).function("nop") {log("hit")}'
Pass 1: parsed user script and 46 library script(s) using
191168virt/9052res/3024shr/5892data kb, in 30usr/0sys/33real ms.
Pass 2: analyzed script: 1 probe(s), 1 function(s), 0 embed(s), 0 global(s)
using 191432virt/9928res/3668shr/6156data kb, in 0usr/0sys/1real ms.
Pass 3: translated to C into
"/tmp/stapYU8fAJ/stap_44550b941b2325a0d3f7b68946033d80_1095_src.c" using
191696virt/10528res/4064shr/6420data kb, in 10usr/50sys/62real ms.
Pass 4: compiled C into "stap_44550b941b2325a0d3f7b68946033d80_1095.so" in
600usr/20sys/633real ms.
Pass 5: starting run.
stapdyn: WARNING: process probes require a target (-c or -x)
^CPass 5: run completed in 0usr/10sys/14324real ms.
 7.0 S x86_64 #
-------------------------------8<------------------------------------

This actually breaks the process_by_pid.stp testcase on el7 and f20.

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

             reply	other threads:[~2014-09-05 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05 14:45 mcermak at redhat dot com [this message]
2014-09-05 16:37 ` [Bug dyninst/17352] " jistone at redhat dot com
2018-11-29 16:07 ` 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-17352-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).