Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 5/6] New MI command -trace-frame-collected
Date: Thu, 13 Jun 2013 14:27:00 -0000	[thread overview]
Message-ID: <83obbaw425.fsf@gnu.org> (raw)
In-Reply-To: <1371086914-8398-6-git-send-email-yao@codesourcery.com>

> From: Yao Qi <yao@codesourcery.com>
> Date: Thu, 13 Jun 2013 09:28:33 +0800
> 
> This patch adds the new MI command -trace-frame-collected, which can
> dump explicitly collected variables, computed expressions, tvars,
> memory and registers.  See details in the doc about MI command
> options.

Thanks.

> diff --git a/gdb/NEWS b/gdb/NEWS
> index 2c66db7..d480f45 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -80,6 +80,10 @@ show range-stepping
>       "--skip-unavailable" option.  When used, only the available registers
>       are displayed.
>  
> +  ** The new command -trace-frame-collected dumps explicitly collected
> +     variables, computed expressions, tvars, memory and registers in a
> +     traceframe.
> +

This is OK.

> +This command returns the set of explicitly wholly collected objects,

What is meant by "explicitly wholly collected objects"?  That phrase
got me confused, especially the "wholly" part.

> +For instance, if the actions were @code{myVar, myArray[myIndex]
> +myObj.field, myPtr->field, myCount + 2, *(int*)0xaf02bef0@@40}, the

It is better to put the code part in @smallexample.

> +@item computed-expressions
> +The set of computed expressions that have been collected at the
> +current trace frame.  The @code{--comp-print-values} option affects
> +this set, as the @code{--var-print-values} option affects the
             ^^
"like", not "as".  And you don't need the comma before that.

OK with the above changes, and assuming we resolve the "wholly" issue.


  reply	other threads:[~2013-06-13 13:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 13:07 [PATCH 0/5] " Yao Qi
2013-06-07 13:07 ` [PATCH 1/5] Remove global variable tracepoint_list and stepping_list Yao Qi
2013-06-07 20:50   ` Pedro Alves
2013-06-07 13:07 ` [PATCH 4/5] New MI command -trace-frame-collected Yao Qi
2013-06-07 13:07 ` [PATCH 5/5] New test: gdb.trace/mi-trace-frame-collected.exp Yao Qi
2013-06-07 13:07 ` [PATCH 3/5] Add id of TSV into traceframe_info Yao Qi
2013-06-07 14:39   ` Eli Zaretskii
2013-06-08 11:06     ` Yao Qi
2013-06-07 13:07 ` [PATCH 2/5] Move code to get_traceframe_location Yao Qi
2013-06-07 21:09   ` Pedro Alves
2013-06-13  1:29 ` [PATCH 0/6 V2] New MI command -trace-frame-collected Yao Qi
2013-06-13  1:29   ` [PATCH 3/6] Move code to get_traceframe_location Yao Qi
2013-06-25 15:43     ` Pedro Alves
2013-06-13  1:29   ` [PATCH 6/6] New test: gdb.trace/mi-trace-frame-collected.exp Yao Qi
2013-06-25 18:42     ` Pedro Alves
2013-06-26 10:32       ` Yao Qi
2013-06-13  1:29   ` [PATCH 5/6] New MI command -trace-frame-collected Yao Qi
2013-06-13 14:27     ` Eli Zaretskii [this message]
2013-06-14  9:52       ` Yao Qi
2013-06-14 12:34         ` Eli Zaretskii
2013-06-17 10:21           ` Yao Qi
2013-06-17 15:48             ` Eli Zaretskii
2013-06-18 14:09               ` Yao Qi
2013-06-18 17:24                 ` Eli Zaretskii
2013-06-25 17:31                 ` Pedro Alves
2013-06-26  8:29                   ` Yao Qi
2013-06-26 11:22                     ` Pedro Alves
2013-06-13  1:29   ` [PATCH 2/6] Emit error in tdump command when traceframe is not selected Yao Qi
2013-06-25 15:32     ` Pedro Alves
2013-06-13  1:29   ` [PATCH 4/6] Add id of TSV into traceframe_info Yao Qi
2013-06-13  3:40     ` Eli Zaretskii
2013-06-25 16:18     ` Pedro Alves
2013-06-26  8:19       ` Yao Qi
2013-06-13  2:46   ` [PATCH 1/6] Remove global variable tracepoint_list and stepping_list Yao Qi
2013-06-25 15:28     ` Pedro Alves
2013-06-24 15:25   ` [ping]: [PATCH 0/6 V2] New MI command -trace-frame-collected 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=83obbaw425.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