From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Conditional tracepoints
Date: Tue, 30 Jun 2009 03:06:00 -0000 [thread overview]
Message-ID: <83fxdi4e0c.fsf@gnu.org> (raw)
In-Reply-To: <4A492432.8010600@codesourcery.com>
> Date: Mon, 29 Jun 2009 13:29:38 -0700
> From: Stan Shebs <stan@codesourcery.com>
> CC: Stan Shebs <stan@codesourcery.com>, gdb-patches@sourceware.org
>
> >> ! (@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.
Fine with me; in that case, this text should use the same terminology
as "Agent Expressions" and perhaps have a cross-reference to there.
> >> + @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. :-)
They are still more descriptive than "tests" in this context, IMO.
Thanks.
next prev parent reply other threads:[~2009-06-30 3:06 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
2009-06-30 3:06 ` Eli Zaretskii [this message]
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=83fxdi4e0c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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