public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "peter at peca dot dk" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/17623] Sometimes probes fail to fire events when running against a multi-threaded application
Date: Thu, 20 Nov 2014 07:49:00 -0000	[thread overview]
Message-ID: <bug-17623-6586-rhzEsd1auN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17623-6586@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Peter Allin <peter at peca dot dk> ---
(In reply to Frank Ch. Eigler from comment #2)
> Peter, have you by any chance tried out "perf probe" against your
> original binary, to see if this is may be a kernel-side rather
> than stap-side problem?

I have just tried it, and am somewhat confused by the results. Here is what I
did:

- perf probe -x testprog func1
- perf probe -x testprog func2
- Start testprog in another terminal
- perf stat -e probe_testprog:func1 -e probe_testprog:func2 -a sleep 1

I ran the last command in a loop for 1000 times. It always shows counts for
both probe points, but the counts are not equal. So it seems that SystemTap
will either work perfectly or loose all events from one of the probes, while
perf is always missing some events but not all.

Do you think this is caused by two separate problems, or are both pointing
towards a kernel problem?

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

  parent reply	other threads:[~2014-11-20  7:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 13:51 [Bug uprobes/17623] New: " peter at peca dot dk
2014-11-19 13:51 ` [Bug uprobes/17623] " peter at peca dot dk
2014-11-19 14:39 ` fche at redhat dot com
2014-11-20  7:49 ` peter at peca dot dk [this message]
2014-11-20  7:54 ` peter at peca dot dk
2014-11-20 17:04 ` dsmith at redhat dot com
2014-11-21  7:31 ` peter at peca dot dk
2014-11-21 14:45 ` dsmith at redhat dot com
2014-11-23  7:40 ` peter at peca dot dk
2014-11-23  7:53 ` peter at peca dot dk
2014-11-23 16:49 ` peter at peca dot dk
2014-11-24 15:17 ` dsmith at redhat dot com
2014-11-25 10:24 ` peter at peca dot dk
2021-05-03 22:34 ` 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-17623-6586-rhzEsd1auN@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).