From: Hui Zhu <hui_zhu@mentor.com>
To: <gdb-patches@sourceware.org>
Cc: <lgustavo@codesourcery.com>, Pedro Alves <palves@redhat.com>,
Eli Zaretskii <eliz@gnu.org>
Subject: [PATCH] Support targets that know how to continue over breakpoints[2/4] -- Doc
Date: Sat, 02 Mar 2013 16:11:00 -0000 [thread overview]
Message-ID: <513224AF.6030603@mentor.com> (raw)
In-Reply-To: <51322425.6090007@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 337 bytes --]
Hello,
This is the doc patch for continue over breakpoints function.
Please help me review it.
Thanks,
Hui
2013-03-03 Luis Machado <lgustavo@codesourcery.com>
Pedro Alves <pedro@codesourcery.com>
Hui Zhu <hui_zhu@mentor.com>
* gdb.texinfo (General Query Packets): Document
ContinueOverBreakpoints under qSupported.
[-- Attachment #2: remote-cob-doc.txt --]
[-- Type: text/plain, Size: 1047 bytes --]
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -37383,6 +37383,11 @@ These are the currently defined stub fea
@tab @samp{-}
@tab No
+@item @samp{ContinueOverBreakpoints}
+@tab No
+@tab @samp{-}
+@tab No
+
@end multitable
These are the currently defined stub features, in more detail:
@@ -37537,6 +37542,15 @@ See @ref{Bytecode Descriptions} for deta
The remote stub supports running a breakpoint's command list itself,
rather than reporting the hit to @value{GDBN}.
+@item ContinueOverBreakpoints
+The remote stub knows how to continue over breakpoints itself. 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
+only applies to continue requests. This feature is only defined when the
+remote stub supports managing breakpoints itself (see @ref{insert
+breakpoint or watchpoint packet}). @value{GDBN} assumes that this feature
+is applicable to all breakpoints types supported by the stub.
+
@end table
@item qSymbol::
next prev parent reply other threads:[~2013-03-02 16:11 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 ` Hui Zhu [this message]
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 ` [PATCH] Support targets that know how to continue over breakpoints[2/4] -- Doc Eli Zaretskii
2013-03-03 2:06 ` 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=513224AF.6030603@mentor.com \
--to=hui_zhu@mentor.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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