16:46 <irker079> systemtap: dsmith systemtap.git:refs/heads/dsmith/python * release-3.0-345-gaa33c8e / python/stap-resolve-module-function.py: Improve python probe listing. http://tinyurl.com/zhn6hxm

16:56 <irker079> systemtap: dsmith systemtap.git:refs/heads/dsmith/python * release-3.0-346-g21745df / testsuite/lib/systemtap.exp testsuite/systemtap.base/listing_mode.exp testsuite/systemtap.base/listing_mode.py testsuite/systemtap.unprivileged/test.py testsuite/systemtap.unprivileged/unprivileged_probes.exp: Add python 2 and python3 probe support to existing tests. http://tinyurl.com/ztkn5kk

17:28 <irker079> systemtap: dsmith systemtap.git:refs/heads/master * release-3.0-307-gda79853 / testsuite/systemtap.pass1-4/semko.exp: Avoid creating a file called '&1' in testsuite/systemtap.pass1-4/semko.exp. http://tinyurl.com/ze3xcrt

21:57 <frdeso> Hi all, I am new to Systemtap. When tracing USDT probes, when a probe is triggered is a kernel module involved to gather the payload of the probe ? Also, is there any documentation on the implementation of the USDT support?

21:58 <fche> frdeso, hi

21:58 <fche> the implementation of the instrumentation per se is a separate thing from how the instrumentation is used at run time

22:00 <fche> https://sourceware.org/systemtap/wiki/UserSpaceProbeImplementation <-- former

22:01 <fche> the latter - depends on which stap --runtime is chosen; in the default kernel-module-based one, yes, the kernel will trap on the NOPs that the instrumentation leaves in object code

22:01 <fche> in --runtime=dyninst, no kernel is involved, but instead some run-time binary rewriting is done

22:01 <fche> https://sourceware.org/gdb/onlinedocs/gdb/Static-Probe-Points.html <-- see also how gdb can access the data too

22:04 <fche> frdeso, for more specific questions, pls send mail to the mailing list

22:42 <frdeso> fche: thank you very much! I will have a look at the links you sent

22:50 <fche> righto