Re: [patch 5/5] Document

[Luis Machado <luis_gustavo at mentor dot com>]

Hi,

Just a suggestion on the documentation text.

On 11/15/2011 06:07 AM, Yao Qi wrote:
> This is the documentation about pending tracepoint.
>
> -- Yao (éå)
>
>
> 0005-doc-pending-tracepoint.patch
>
>
>
> 	* gdb.texinfo (Create and Delete Tracepoints): Mention pending
> 	tracepoint.
> ---
>   gdb/doc/gdb.texinfo |    8 +++++++-
>   1 files changed, 7 insertions(+), 1 deletions(-)
>
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 0cadc96..979b2e4 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -10337,7 +10337,13 @@ in tracing}).
>   If remote stub doesn't support the @samp{InstallInTrace} feature, all
>   these changes don't take effect until the next @code{tstart}
>   command, and once a trace experiment is running, further changes will
> -not have any effect until the next trace experiment starts.
> +not have any effect until the next trace experiment starts.  Similar
> +to breakpoint, @dfn{pending tracepoint}---tracepoint whose address is
to breakpoints, @dfn{pending tracepoint}---tracepoints whose addresses are

> +not yet resolved, is supported as well.  Pending tracepoint is not
not yet resolved are supported as well.  Pending tracepoints are not

> +downloaded to target and not installed until it is resolved.  The
downloaded to and installed on the target until they are resolved.  The

> +resolution of pending tracepoint requires @value{GDBN} support.  In
resolution of pending tracepoints require @value{GDBN} support.  In

> +remote target, when @value{GDBN} disconnects from remote stub, pending
the remote target, when @value{GDBN} disconnects from the remote stub, 
pending

> +tracepoint still exists but can not be resolved during disconnection.
tracepoints still exist but will not be resolved until @value{GDBN} 
reconnects to it.

>   Here are some examples of using the @code{trace} command:
>
> -- 1.7.0.4