From: jose.marchesi@oracle.com (Jose E. Marchesi)
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/9] New gdbarch functions: dtrace_probe_argument, dtrace_probe_is_enabled, dtrace_enable_probe, dtrace_disable_probe.
Date: Fri, 10 Oct 2014 16:38:00 -0000 [thread overview]
Message-ID: <871tqfev6n.fsf@oracle.com> (raw)
In-Reply-To: <874mvmupep.fsf@redhat.com> (Sergio Durigan Junior's message of "Thu, 02 Oct 2014 17:34:22 -0400")
> diff --git a/gdb/gdbarch.sh b/gdb/gdbarch.sh
> index 2a8bca8..0458134 100755
> --- a/gdb/gdbarch.sh
> +++ b/gdb/gdbarch.sh
> @@ -944,6 +944,21 @@ M:int:stap_is_single_operand:const char *s:s
> # parser), and should advance the buffer pointer (p->arg).
> M:int:stap_parse_special_token:struct stap_parse_info *p:p
>
> +# DTrace related functions.
> +
> +# The expression to compute the NARTGth+1 argument to a DTrace USDT probe.
> +# NARG must be >= 0.
> +M:void:dtrace_probe_argument:struct parser_state *pstate, int narg:pstate, narg
This function is responsible for parsing the argument, right? I'd
prefer if you named it "dtrace_parse_probe_argument". WDYT?
Yes, I agree, that name is better. Changed in the patch.
next prev parent reply other threads:[~2014-10-10 16:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <no>
2012-04-18 9:27 ` [RFA] Add proper handling for internal functions and STT_GNU_IFUNC symbols in Ada mode Paul Hilfinger
2012-04-18 14:45 ` Joel Brobecker
2012-04-22 15:33 ` [committed] " Paul Hilfinger
2014-09-26 9:43 ` [PATCH 0/9] Add support for DTrace USDT probes to gdb Jose E. Marchesi
2014-09-26 9:43 ` [PATCH 8/9] Documentation for DTrace USDT probes Jose E. Marchesi
2014-09-26 13:18 ` Eli Zaretskii
2014-09-29 10:26 ` Jose E. Marchesi
2014-09-29 13:35 ` Eli Zaretskii
2014-09-29 13:53 ` Jose E. Marchesi
2014-09-26 9:43 ` [PATCH 5/9] New probe type: " Jose E. Marchesi
2014-09-26 13:19 ` Eli Zaretskii
2014-10-02 23:19 ` Sergio Durigan Junior
2014-10-10 16:38 ` Jose E. Marchesi
2014-10-10 18:13 ` Sergio Durigan Junior
2014-10-10 18:32 ` Jose E. Marchesi
2014-10-10 18:44 ` Sergio Durigan Junior
2014-09-26 9:43 ` [PATCH 3/9] New commands `enable probe' and `disable probe' Jose E. Marchesi
2014-09-26 13:11 ` Eli Zaretskii
2014-09-29 10:26 ` Jose E. Marchesi
2014-09-30 23:13 ` Sergio Durigan Junior
2014-09-30 23:20 ` Sergio Durigan Junior
2014-10-10 16:38 ` Jose E. Marchesi
2014-09-26 9:43 ` [PATCH 6/9] Support for DTrace USDT probes in x86_64 targets Jose E. Marchesi
2014-10-08 19:32 ` Sergio Durigan Junior
2014-10-10 16:38 ` Jose E. Marchesi
2014-09-26 9:43 ` [PATCH 9/9] Announce the DTrace USDT probes support in NEWS Jose E. Marchesi
2014-09-26 13:12 ` Eli Zaretskii
2014-09-29 10:29 ` Jose E. Marchesi
2014-09-26 9:43 ` [PATCH 7/9] Simple testsuite for DTrace USDT probes Jose E. Marchesi
2014-10-08 19:30 ` Sergio Durigan Junior
2014-10-10 16:38 ` Jose E. Marchesi
2014-09-26 9:43 ` [PATCH 1/9] Adapt `info probes' to support printing probes of different types Jose E. Marchesi
2014-09-29 21:15 ` Sergio Durigan Junior
2014-10-10 16:38 ` Jose E. Marchesi
2014-09-26 9:43 ` [PATCH 2/9] Move `compute_probe_arg' and `compile_probe_arg' to probe.c Jose E. Marchesi
2014-09-30 0:02 ` Sergio Durigan Junior
2014-10-10 16:38 ` Jose E. Marchesi
2014-09-26 9:43 ` [PATCH 4/9] New gdbarch functions: dtrace_probe_argument, dtrace_probe_is_enabled, dtrace_enable_probe, dtrace_disable_probe Jose E. Marchesi
2014-10-02 21:34 ` Sergio Durigan Junior
2014-10-10 16:38 ` Jose E. Marchesi [this message]
2014-10-08 19:40 ` [PATCH 0/9] Add support for DTrace USDT probes to gdb Sergio Durigan Junior
2014-10-09 8:05 ` 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=871tqfev6n.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).