From: Stan Shebs <stan@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stan Shebs <stan@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Conditional tracepoints
Date: Mon, 29 Jun 2009 20:29:00 -0000 [thread overview]
Message-ID: <4A492432.8010600@codesourcery.com> (raw)
In-Reply-To: <83fxdlzvin.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Fri, 26 Jun 2009 22:31:07 -0700
>> From: Stan Shebs <stan@codesourcery.com>
>>
>> This patch adds conditional tracepoints.
>>
>
> Thanks.
>
> I think we need a NEWS entry for this.
>
OK, good idea.
>> + programming language (@pxref{Expressions, ,Expressions}). A
>> + tracepoint with a condition evaluates the expression each time your
>> + program reaches it, and data collection happens only if the condition
>> + is @emph{true}.
>>
>
> Not sure why you use the @emph markup here. I think the text is okay
> without any markup at all.
>
It's been several months since I wrote it, and now I don't remember
either. :-)
>
>> @table @code
>> @kindex maint agent
>> + @kindex maint agent-eval
>> @item maint agent @var{expression}
>> + @itemx maint agent-eval @var{expression}
>> Translate the given @var{expression} into remote agent bytecodes.
>> This command is useful for debugging the Agent Expression mechanism
>> ! (@pxref{Agent Expressions}). The @samp{agent} version produces an
>> ! expression useful for data collection, such as by tracepoints, while
>> ! @samp{maint agent-eval} produces an expression that evaluates directly
>> ! to a result.
>>
>
> I must admit that I don't understand the description you added. What
> does "expression useful for data collection" mean, and how is it
> different from "expression that evaluates directly to a result"?
>
Expressions compiled for tracing have bytecodes that cause saving of the
blocks of memory etc that would be needed back on the host to evaluate
the expression at some later date. It occurs to me that the Agent
Expressions section should say a little more about the two kind of
expressions.
>> + @item ConditionalTracepoints
>> + The remote stub accepts and tests conditional expressions defined for
>> + tracepoints (@pxref{Tracepoint Conditions}).
>>
>
> Don't you mean "accepts and supports" or "accepts and implements"?
>
"support" and "implement" seemed overused. :-)
Stan
next prev parent reply other threads:[~2009-06-29 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 5:31 Stan Shebs
2009-06-27 12:55 ` Eli Zaretskii
2009-06-29 20:29 ` Stan Shebs [this message]
2009-06-30 3:06 ` Eli Zaretskii
2009-06-29 16:38 ` Tom Tromey
2009-06-29 20:58 ` Stan Shebs
2009-06-29 21:50 ` Tom Tromey
2009-07-14 23:29 ` Stan Shebs
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=4A492432.8010600@codesourcery.com \
--to=stan@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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