[PATCH V3 8/9] Documentation for DTrace USDT probes.

[Ed Maste]

On 28 October 2014 at 09:49, Jose E. Marchesi <jose.marchesi@oracle.com> wrote:
> +Some @code{SystemTap} probes have an associated semaphore variable;
> +for instance, this happens automatically if you defined your probe
> +using a DTrace-style @file{.d} file.  If your probe has a semaphore,
> +@value{GDBN} will automatically enable it when you specify a
> +breakpoint using the @samp{-probe-stap} notation.  But, if you put a
> +breakpoint at a probe's location by some other method (e.g.,
> +@code{break file:line}), then @value{GDBN} will not automatically set
> +the semaphore.  @code{DTrace} probes do not support semaphores.

This seems confusing to me now that there is additional DTrace context
in this paragraph: something unsupported by DTrace happens
automatically when using a DTrace-style .d file. Would something like
"a standalone probe definition file" be better than "DTrace-style"?