Francis Deslauriers added the comment:
Hi all,
It seems that, as of right now, the thing blocking this patchset from
going forward is the name of the intrumentation point.
Two naming approached were suggested:
- Keeping PyDtrace*
- Changing to PyProbe*
I prefer the PyProbe
Francis Deslauriers added the comment:
Hi all,
Is there anything I can do to move this patch-set forward?
@Charalampos, I will make sure to include this in the patch. Thank you.
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.p
Francis Deslauriers added the comment:
Here is the documentation patch.
--
Added file:
http://bugs.python.org/file46695/0003-Documentation-of-LTTng-UST-tracing-instrumentation.patch
___
Python tracker <rep...@bugs.python.org>
<http://bugs.p
Francis Deslauriers added the comment:
> What about `PyProbe`? Given the multitude of tools and techniques in this
> space, wouldn't it be worthwhile to clarify things before adding this? I
> think conflating `dtrace` and `lttng` would only lead to more confusion for
> users as
Francis Deslauriers added the comment:
I am finally having the time to work in this.
> A nit: the name LTTng-UST is rather unfriendly, especially when used without
> the dash and in all lowercase characters. Given that we're using "dtrace" and
> "systemtap", it
Francis Deslauriers added the comment:
Thanks Łukasz,
I will add tests following the example of the DTrace tests and update the
Doc/howto/instrumentation.rst file to include this new information.
LTTng can be used on all major Linux distros (Ubuntu, Debian, Fedora, etc.)
either from
Changes by Francis Deslauriers <fdesl...@gmail.com>:
--
nosy: +jcea
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28909>
___
_
New submission from Francis Deslauriers:
This patch extends the tracing infrastructure to support LTTng UserSpace
Tracer. Using LTTng-UST, users would have access to a low overhead tracing
done entirely from userspace.
Depending on the tracing configure option used (none, --with-dtrace
