From: Ed Maste <emaste@freebsd.org>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: gdb@sourceware.org
Subject: Re: [PATCH V3 8/9] Documentation for DTrace USDT probes.
Date: Wed, 04 Feb 2015 16:21:00 -0000 [thread overview]
Message-ID: <CAPyFy2AAS8k8pY2Z-n8qWbOJhFn2kxsDdTrGtBc=yvVS9MeFbg@mail.gmail.com> (raw)
In-Reply-To: <1414504151-31155-9-git-send-email-jose.marchesi@oracle.com>
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"?
next prev parent reply other threads:[~2015-02-04 16:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 13:44 [PATCH V3 0/9] Add support for DTrace USDT probes to gdb Jose E. Marchesi
2014-10-28 13:44 ` [PATCH V3 5/9] New probe type: DTrace USDT probes Jose E. Marchesi
2014-10-28 13:44 ` [PATCH V3 9/9] Announce the DTrace USDT probes support in NEWS Jose E. Marchesi
2014-10-28 16:13 ` Eli Zaretskii
2014-10-28 13:44 ` [PATCH V3 7/9] Simple testsuite for DTrace USDT probes Jose E. Marchesi
2014-10-28 13:44 ` [PATCH V3 3/9] New commands `enable probe' and `disable probe' Jose E. Marchesi
2014-10-28 16:08 ` Eli Zaretskii
2014-10-28 13:44 ` [PATCH V3 6/9] Support for DTrace USDT probes in x86_64 targets Jose E. Marchesi
2014-10-28 13:44 ` [PATCH V3 1/9] Adapt `info probes' to support printing probes of different types Jose E. Marchesi
2014-10-28 14:06 ` Jose E. Marchesi
2014-10-28 13:44 ` [PATCH V3 8/9] Documentation for DTrace USDT probes Jose E. Marchesi
2014-10-28 16:13 ` Eli Zaretskii
2015-02-04 16:21 ` Ed Maste [this message]
2014-10-28 13:44 ` [PATCH V3 2/9] Move `compute_probe_arg' and `compile_probe_arg' to probe.c Jose E. Marchesi
2014-10-28 13:44 ` [PATCH V3 4/9] New gdbarch functions: dtrace_parse_probe_argument, dtrace_probe_is_enabled, dtrace_enable_probe, dtrace_disable_probe Jose E. Marchesi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPyFy2AAS8k8pY2Z-n8qWbOJhFn2kxsDdTrGtBc=yvVS9MeFbg@mail.gmail.com' \
--to=emaste@freebsd.org \
--cc=gdb@sourceware.org \
--cc=jose.marchesi@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox