From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] traceframe_changed observer and MI notification
Date: Tue, 18 Sep 2012 06:53:00 -0000 [thread overview]
Message-ID: <83pq5j257w.fsf@gnu.org> (raw)
In-Reply-To: <5057BB72.9070305@codesourcery.com>
> Date: Tue, 18 Sep 2012 08:08:18 +0800
> From: Yao Qi <yao@codesourcery.com>
> CC: Eli Zaretskii <eliz@gnu.org>
>
> On 08/31/2012 05:09 PM, Yao Qi wrote:
> > gdb/doc:
> >
> > * observer.texi (GDB Observers): New observer 'traceframe_changed'.
> > * gdb.texinfo (GDB/MI Async Records): Mention new MI notification
> > '=traceframe-changed'.
>
> Eli,
> Could you review the doc part of this patch?
> http://sourceware.org/ml/gdb-patches/2012-08/msg00885.html
Sorry about the delay. Here goes:
> +@item =traceframe-changed,num=@var{tfnum},tracepoint=@var{tpnum}
> +@itemx =traceframe-changed,end
> +Reports that the traceframe is changed and its number is @var{tfnum}.
I suggest to reword:
Reports that the trace frame was changed, and its new number is @var{tfnum}.
> +or @value{GDBN} stops examining traceframes and resumes live debugging.
This line should be edited to explain the meaning of negative values
of tfnum.
> +The number of the tracepoint associated with this traceframe is
> +@var{tpnum}. ^^^^^^^^^^
"trace frame"
> +@deftypefun void traceframe_changed (int @var{tfnum}, int @var{tpnum})
> +The traceframe is changed to @var{tfnum} in command @code{tfind}.
^^^^^^^^^^
"trace frame"
Also, I don't understand the significance of the reference to
'tfind'. Why is it important to mention that?
> +The number of the tracepoint associated with this traceframe is
> +@var{tpnum}. When @var{tfnum} is negative, @value{GDBN} resumes
> +live debugging.
The last sentence should follow the description of tfnum. I would
also rephrase it:
If var{tfnum} is negative, it means @value{GDBN} resumes live debugging.
Thanks.
next prev parent reply other threads:[~2012-09-18 6:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 9:10 Yao Qi
2012-09-07 6:59 ` [ping]: " Yao Qi
2012-09-10 18:52 ` Tom Tromey
2012-09-11 13:38 ` Yao Qi
2012-09-11 15:28 ` Tom Tromey
2012-09-18 0:09 ` Yao Qi
2012-09-18 6:53 ` Eli Zaretskii [this message]
2012-09-18 7:24 ` Yao Qi
2012-09-18 8:01 ` Eli Zaretskii
2012-09-18 8:48 ` Yao Qi
2012-09-18 9:42 ` Eli Zaretskii
2012-09-18 11:42 ` Yao Qi
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=83pq5j257w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@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