linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: HOUSSEN Franck <fghoussen@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Can not trace perf-probe event (made to probe the main function) with perf-top
Date: Sun, 20 Nov 2016 22:26:17 +0900	[thread overview]
Message-ID: <20161120222617.39bc8304001c7690f82d52b4@kernel.org> (raw)
In-Reply-To: <CABvthiqxj=FCj-hg1Bhdnx=sTMZVt78nAM_N89HuuzfkBf7ZJw@mail.gmail.com>

Hello Franck,

On Sat, 19 Nov 2016 17:36:39 +0100
HOUSSEN Franck <fghoussen@gmail.com> wrote:

> Can not trace perf-probe event (made to probe the main function) with
> perf-top ? (see ReadMe.txt - works with perf-report and -s option)
> Can someone help ? Missing option ? Known bug / limitation ?

From ReadMe.txt;
----
~> sudo perf top -K --stdio -s sym,dso -e probe_main:main
   PerfTop:       0 irqs/sec  kernel: 0.0%  exact:  0.0% [1Hz probe_main:main],  (all, 4 CPUs)
   -------------------------------------------------------------------------------------------
----
Have you tried to run ./main program while running "perf top"?

Since the main function is just called once when starting run
the main program, without invoking it, the probe_main:main
may never be occured.

Thanks,
-- 
Masami Hiramatsu <mhiramat@kernel.org>

  reply	other threads:[~2016-11-20 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-19 16:36 Can not trace perf-probe event (made to probe the main function) with perf-top HOUSSEN Franck
2016-11-20 13:26 ` Masami Hiramatsu [this message]
2016-11-21 10:35   ` HOUSSEN Franck

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=20161120222617.39bc8304001c7690f82d52b4@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=fghoussen@gmail.com \
    --cc=linux-perf-users@vger.kernel.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 NNTP newsgroup(s).