Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, Luis Machado <luis_gustavo@mentor.com>
Subject: Re: [patch 5/5] Document
Date: Wed, 16 Nov 2011 03:13:00 -0000	[thread overview]
Message-ID: <4EC32A42.7090500@codesourcery.com> (raw)
In-Reply-To: <83d3cte2rr.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

On 11/16/2011 01:03 AM, Eli Zaretskii wrote:
>> > +                                                              Similar
>> > +to breakpoint, @dfn{pending tracepoint}---tracepoint whose address is
>> > +not yet resolved, is supported as well.
> Putting verbs at the end of the sentence produces awkward and hard to
> understand sentences (unless you talk in German or Japanese ;-).

This applies to Chinese as well :)

> Using passive tense makes it even more so.  I would reword like this:
> 
>   In addition, @value{GDBN} supports @dfn{pending tracepoints}---
>   tracepoints whose address is not yet resolved.  (This is similar to
>   pending breakpoints.)

That looks good.

Eli, Luis,
Thanks for your suggestions.  Here is a new one.

-- 
Yao (齐尧)

[-- Attachment #2: 0005-doc-pending-tracepoint.patch --]
[-- Type: text/x-patch, Size: 1236 bytes --]


	* gdb.texinfo (Create and Delete Tracepoints): Mention pending
	tracepoint.
---
 gdb/doc/gdb.texinfo |    9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 0cadc96..6882b78 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -10337,7 +10337,14 @@ 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.  In addition,
+@value{GDBN} supports @dfn{pending tracepoints}---tracepoints whose
+address is not yet resolved.  (This is similar to pending breakpoints.)
+Pending tracepoints are not downloaded to target and not installed until
+they are resolved.  The resolution of pending tracepoints requires
+@value{GDBN} support.  In the remote target, when @value{GDBN}
+disconnects from remote stub, pending tracepoints still exists but can
+not be resolved while @value{GDBN} is disconnected.
 
 Here are some examples of using the @code{trace} command:
 
-- 
1.7.0.4


  reply	other threads:[~2011-11-16  3:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15  7:01 [patch 0/5] pending tracepoint Yao Qi
2011-11-15  7:30 ` [patch 1/5] Call update_global_location_list conditionally in install_breakpoint Yao Qi
2011-11-16 19:04   ` Pedro Alves
2011-11-15  7:43 ` [patch 2/5] allow pending tracepoint Yao Qi
2011-11-16 19:04   ` Pedro Alves
2011-11-17  1:12     ` Yao Qi
2011-11-15  7:47 ` [patch 3/5] Print a message on gdb disconnected Yao Qi
2011-11-15 15:32   ` Tom Tromey
2011-11-16  3:17     ` Yao Qi
2011-11-16 19:04   ` Pedro Alves
2011-11-17  3:32     ` Yao Qi
2011-11-17 11:08       ` Pedro Alves
2011-11-15  8:03 ` [patch 4/5] Test cases Yao Qi
2011-11-16 19:05   ` Pedro Alves
2011-11-17  3:27     ` Yao Qi
2011-11-17 12:08       ` Pedro Alves
2011-11-17 14:09         ` Yao Qi
2011-11-17 14:54           ` Pedro Alves
2011-11-15  8:08 ` [patch 5/5] Document Yao Qi
2011-11-15 14:29   ` Luis Machado
2011-11-15 14:57     ` Yao Qi
2011-11-15 15:04       ` Luis Machado
2011-11-15 17:02         ` Eli Zaretskii
2011-11-15 17:06   ` Eli Zaretskii
2011-11-16  3:13     ` Yao Qi [this message]
2011-11-16  4:01       ` Eli Zaretskii
2011-11-16 19:04       ` Pedro Alves
2011-11-17  3:25         ` Yao Qi
2011-11-17 12:28           ` Pedro Alves
2011-11-17 14:31             ` Yao Qi
2011-11-17 14:41               ` Pedro Alves
2011-11-17 15:17                 ` 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=4EC32A42.7090500@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=luis_gustavo@mentor.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