16:24 <dhaibhidh> I'm finding an issue where if I define more than one probe either at function calls within a single function or statements within a function, only the first probe seems to take be triggered. Subsequent probes can be triggered but at much lower frequency. Is this expected behavior?

16:25 <fche2> not really - assuming that the function you're probing is straight-through - that there isn't another explanation like control flow differences to explain the probe rates

16:26 <fche2> that said, there was a kernel bug a couple of months ago that manifested itself with probes being enabled or disabled depending on the order in which they were registered (-> listed in the .stp file)

16:26 <dhaibhidh> This might be my case, the first probe, i.e highest in the file is the one that takes effect.

16:26 <fche2> run with stap -t ... to see hit counts at shutdown

16:27 <fche2> could use the eventcount.stp

16:27 <fche2> sample to see rates live

16:29 <dhaibhidh> Adding stap -t the hit rates and the output look correct.

16:40 <irker003> systemtap: fche systemtap.git:refs/heads/master * release-3.3-29-g5826dc3 / runtime/common_probe_context.h tapset/linux/aux2_syscalls.stp tapset/linux/sysc_read.stp tapset/x86_64/registers.stp tapsets.cxx: PR23160,PR14690: 32-on-64 bit fixes http://tinyurl.com/ydd4teuc