This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug uprobes/17623] Sometimes probes fail to fire events when running against a multi-threaded application


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]