From: "dsmith at redhat dot com" <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 17:04:00 -0000 [thread overview]
Message-ID: <bug-17623-6586-3sftt20tHJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17623-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17623
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dsmith at redhat dot com
--- Comment #5 from David Smith <dsmith at redhat dot com> ---
Created attachment 7955
--> https://sourceware.org/bugzilla/attachment.cgi?id=7955&action=edit
2nd test script
On my F20 vm (3.16.3-200.fc20.x86_64), your test program and script worked fine
(even at WAIT_US 1). What kernel are you running?
When you finally stopped systemtap, did it report any skipped probes?
I've attached a modified test script that I'd like you to try. In case you are
overrunning the print system, this version just has counters. When you
interrupt systemtap, it will print the count of each function hit. For me for
instance with HEAD systemtap, it reports the following:
When I ran 'stap test2.stp -c ./foobar', I get:
func1: 207326 hits, func2: 207325 hits
When I ran './foobar &; stap test2.stp', I get:
func1: 173137 hits, func2: 173137 hits
Depending on what you get with test2.stp, can I ask you to try with HEAD
systemtap and see what you get?
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-11-20 17:04 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
2014-11-20 7:54 ` peter at peca dot dk
2014-11-20 17:04 ` dsmith at redhat dot com [this message]
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-3sftt20tHJ@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).