From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Add autoload-breakpoints [6/6] autoload-breakpoints doc
Date: Wed, 18 Apr 2012 18:56:00 -0000 [thread overview]
Message-ID: <834nsgkh28.fsf@gnu.org> (raw)
In-Reply-To: <4F8E9D3A.5000809@mentor.com>
> Date: Wed, 18 Apr 2012 18:53:46 +0800
> From: Hui Zhu <hui_zhu@mentor.com>
>
> +about autoload-breakpints from the stub.
^^^^^^^^^^
A typo.
> +enable or disable it. @value{GDBN} will create this breakpoint as
> +it have been created in the target. So when the target create the
> +breakpoint, it need insert this breakpoint with itself. ^^^^^^
^^^^^^^^^^^ ^^^^^^^^^^^
"creates", "needs to insert", and "by itself".
> +@item @var{id}@samp{:}@samp{R}
> +This is the remove packet.
> +@var{id} is the number of the autoload-breakpoint that this command
> +wants to remove, encoded as a hex string.
> +@value{GDBN} will remove this breakpoint as it have been removed in
> +the target.
I don't understand the last sentence. Please explain.
> So when the target remove the breakpoint, it need remove
> +this breakpoint with itself. ^^^^^^ ^^^^^^^^^^^
^^^^^^^^^^^
"removes", "needs to remove", and "by itself".
By the way, what non-trivial information does this sentence convey?
It seems to say "when the target removes the breakpoint, it needs to
remove the breakpoint", which is trivial. What am I missing here?
> +0 means all autoload-breakpoints.
This sentence should be moved right after the sentence that starts
with "@var{id} is the number of the autoload-breakpoint".
Thanks.
next prev parent reply other threads:[~2012-04-18 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 10:55 Hui Zhu
2012-04-18 12:16 ` Hui Zhu
2012-04-18 18:56 ` Eli Zaretskii [this message]
2012-04-19 12:51 ` Hui Zhu
2012-04-19 15:34 ` Eli Zaretskii
2012-04-20 0:06 ` Hui Zhu
2012-04-28 8:25 ` Hui Zhu
2012-04-28 8:33 ` Eli Zaretskii
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=834nsgkh28.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@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