Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: gdb-patches@sourceware.org, lgustavo@codesourcery.com, palves@redhat.com
Subject: Re: [PATCH] Support targets that know how to continue over breakpoints[2/4] -- Doc
Date: Sat, 02 Mar 2013 16:19:00 -0000	[thread overview]
Message-ID: <8338wdvkpl.fsf@gnu.org> (raw)
In-Reply-To: <513224AF.6030603@mentor.com>

> Date: Sun, 3 Mar 2013 00:11:27 +0800
> From: Hui Zhu <hui_zhu@mentor.com>
> CC: <lgustavo@codesourcery.com>, Pedro Alves <palves@redhat.com>, Eli
>  Zaretskii <eliz@gnu.org>
> 
> This is the doc patch for continue over breakpoints function.

Thanks.

> +@item ContinueOverBreakpoints
> +The remote stub knows how to continue over breakpoints itself.

Please remove the "itself" part, it is not needed.

>                                                                 If this
> +feature is supported by the target, then @value{GDBN} does not need to
> +lift breakpoints off of the inferior and step over them.  This feature

 "... @value{GDBN} does not need to remove breakpoints in order to
 step over them."


> +only applies to continue requests. This feature is only defined when the
                                    ^^                     ^^^^^^^
Two spaces here.  And "available" instead of "defined".

> +remote stub supports managing breakpoints itself (see @ref{insert
> +breakpoint or watchpoint packet}).

Please use "@pxref" instead of "see @ref".

>                                    @value{GDBN} assumes that this feature
> +is applicable to all breakpoints types supported by the stub.
                        ^^^^^^^^^^^
"breakpoint", in singular.

OK with those changes.


  parent reply	other threads:[~2013-03-02 16:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-02 16:09 [PATCH] Support targets that know how to continue over breakpoints[1/4] -- GDB Hui Zhu
2013-03-02 16:11 ` [PATCH] Support targets that know how to continue over breakpoints[2/4] -- Doc Hui Zhu
2013-03-02 16:13   ` [PATCH] Support targets that know how to continue over breakpoints[3/4] -- gdbserver Hui Zhu
2013-03-02 16:14     ` [PATCH] Support targets that know how to continue over breakpoints[4/4] -- testsuite Hui Zhu
2013-03-03  2:18       ` Hui Zhu
2013-03-24 14:45         ` Hui Zhu
2013-05-07  2:46           ` Hui Zhu
2013-03-12 10:05       ` Hui Zhu
2013-03-02 16:20     ` [PATCH] Support targets that know how to continue over breakpoints[3/4] -- gdbserver Eli Zaretskii
2013-03-03  2:15       ` Hui Zhu
2013-03-24 14:10         ` Hui Zhu
2013-03-25  3:46           ` Eli Zaretskii
2013-03-25  8:06             ` Hui Zhu
2013-05-07  2:45           ` Hui Zhu
2013-03-12 10:05     ` Hui Zhu
2013-03-02 16:19   ` Eli Zaretskii [this message]
2013-03-03  2:06     ` [PATCH] Support targets that know how to continue over breakpoints[2/4] -- Doc Hui Zhu
2013-03-03  3:51       ` Eli Zaretskii
2013-03-03  3:58         ` Hui Zhu
2013-03-12 10:04   ` Hui Zhu
2013-05-07  2:37     ` Hui Zhu
2013-03-12 10:04 ` [PATCH] Support targets that know how to continue over breakpoints[1/4] -- GDB Hui Zhu
2013-03-24 12:33 ` Hui Zhu
2013-05-07  2:35   ` Hui Zhu

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=8338wdvkpl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.com \
    --cc=lgustavo@codesourcery.com \
    --cc=palves@redhat.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