From: Luis Machado <luis_gustavo@mentor.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 5/5] Document
Date: Tue, 15 Nov 2011 15:04:00 -0000 [thread overview]
Message-ID: <4EC28062.9090506@mentor.com> (raw)
In-Reply-To: <4EC27DAE.9040401@codesourcery.com>
On 11/15/2011 12:56 PM, Yao Qi wrote:
> On 11/15/2011 10:33 PM, Luis Machado wrote:
>>> +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
>>
> I noticed that `pending breakpoint' is in singular form in document, so
> I choose singular form for `pending tracepoint' as well. I am OK with
> either of them.
Should be OK as well. This is a minor suggestion. It just sounded a bit
more natural.
>>> +remote target, when @value{GDBN} disconnects from remote stub, pending
>> the remote target, when @value{GDBN} disconnects from the remote stub,
>> pending
>>
> Right, we need "the" here.
>
>>> +tracepoint still exists but can not be resolved during disconnection.
>> tracepoints still exist but will not be resolved until @value{GDBN}
>> reconnects to it.
> There is a minor difference between yours and mine, IIUC. "will not be
> resolved until GDB reconnects to it" means "pending tracepoints will be
> resolved immediately after GDB reconnects to it", which is not true. We
> don't know when a pending tracepoint can be resolved, but we are sure
> that the pending tracepoint can not be resolved when gdb disconnects.
> What do you think
"will not be resolved until GDB reconnects to it" meant to say that
while GDB is disconnected from the remote target, pending tracepoints
won't be resolved. We can be more explicit about this if the phrasing
isn't clear.
"during disconnection" made it sound like something happens while GDB is
disconnecting.
Maybe "tracepoints still exist but cannot be resolved while GDB is
disconnected?"
Again, these are minor details.
next prev parent reply other threads:[~2011-11-15 15:04 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 [this message]
2011-11-15 17:02 ` Eli Zaretskii
2011-11-15 17:06 ` Eli Zaretskii
2011-11-16 3:13 ` Yao Qi
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=4EC28062.9090506@mentor.com \
--to=luis_gustavo@mentor.com \
--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