SDT probes are known by most as USDT probes. People may be looking for them
by that name.
Reviewed-by: Philippe Proulx <eeppeliteloop@gmail.com>
Signed-off-by: Geneviève Bastien <gbastien+lttng@versatic.net>
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
~~~~~~~~~~~~~~~~~~~~~~~~~
With the option:--userspace-probe option, you can instrument function
entries of any user space binary (application or library) using either
~~~~~~~~~~~~~~~~~~~~~~~~~
With the option:--userspace-probe option, you can instrument function
entries of any user space binary (application or library) using either
-an available symbol name or a SystemTap Statically Defined Tracepoint
-(SDT, a DTrace-style marker) probe's provider and probe names. As of
-this version, only SDT probes that are :not: surrounded by a reference
-counter (semaphore) are supported.
+an available symbol name or a SystemTap User-level Statically Defined
+Tracing (USDT, a DTrace-style marker) probe's provider and probe names.
+As of this version, only USDT probes that are :not: surrounded by a
+reference counter (semaphore) are supported.
The option:--userspace-probe option must be specified with the
option:--kernel option because it uses Linux's uprobe feature to
The option:--userspace-probe option must be specified with the
option:--kernel option because it uses Linux's uprobe feature to
* `--userspace-probe=httpd:ap_run_open_htaccess`
++sdt:++__PATH__++:++__PROVIDER__++:++__NAME__::
* `--userspace-probe=httpd:ap_run_open_htaccess`
++sdt:++__PATH__++:++__PROVIDER__++:++__NAME__::
- Dynamically instrument an SDT probe within a user space application
+ Dynamically instrument a USDT probe within a user space application
`PATH` environment variable.
__PROVIDER__++:++__NAME__::
`PATH` environment variable.
__PROVIDER__++:++__NAME__::
- SDT provider and probe names.
+ USDT provider and probe names.
-For example, with the following SDT probe:
+For example, with the following USDT probe: