aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc
diff options
context:
space:
mode:
authorHui Zhu <teawater@gmail.com>2014-03-21 16:46:15 +0800
committerHui Zhu <teawater@gmail.com>2014-03-21 16:48:52 +0800
commit36cb1214c9f26b4e9b42d146dcf64621b36b91df (patch)
tree02982bd5b0127ebb61510b959e07f990f9ccfb13 /gdb/doc
parentccdd1909ad5299cf0753aaa113928a41f8f27391 (diff)
downloadgdb-36cb1214c9f26b4e9b42d146dcf64621b36b91df.zip
gdb-36cb1214c9f26b4e9b42d146dcf64621b36b91df.tar.gz
gdb-36cb1214c9f26b4e9b42d146dcf64621b36b91df.tar.bz2
Remove fixme of packet "k" from doc
https://sourceware.org/ml/gdb-patches/2014-03/msg00324.html 2014-03-21 Pedro Alves <palves@redhat.com> Stan Shebs <stan@codesourcery.com> Hui Zhu <hui@codesourcery.com> * gdb.texinfo (Packets): Add anchor to "? packet". Remove fixme and update introduction of "k packet". Add anchor to "vKill packet".
Diffstat (limited to 'gdb/doc')
-rw-r--r--gdb/doc/ChangeLog8
-rw-r--r--gdb/doc/gdb.texinfo24
2 files changed, 29 insertions, 3 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 7ba0d21..5095018 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,11 @@
+2014-03-21 Pedro Alves <palves@redhat.com>
+ Stan Shebs <stan@codesourcery.com>
+ Hui Zhu <hui@codesourcery.com>
+
+ * gdb.texinfo (Packets): Add anchor to "? packet".
+ Remove fixme and update introduction of "k packet".
+ Add anchor to "vKill packet".
+
2014-03-12 Stan Shebs <stan@codesourcery.com>
* Doxyfile-gdb-api.in (INPUT): Add gdbtypes.h.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index de5ac63..1df3ca0 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -33742,6 +33742,7 @@ The remote target both supports and has enabled extended mode.
@item ?
@cindex @samp{?} packet
+@anchor{? packet}
Indicate the reason the target halted. The reply is the same as for
step and continue. This packet has a special interpretation when the
target is in non-stop mode; see @ref{Remote Non-Stop}.
@@ -33954,9 +33955,25 @@ step packet}.
@cindex @samp{k} packet
Kill request.
-FIXME: @emph{There is no description of how to operate when a specific
-thread context has been selected (i.e.@: does 'k' kill only that
-thread?)}.
+The exact effect of this packet is not specified.
+
+For a bare-metal target, it may power cycle or reset the target
+system. For that reason, the @samp{k} packet has no reply.
+
+For a single-process target, it may kill that process if possible.
+
+A multiple-process target may choose to kill just one process, or all
+that are under @value{GDBN}'s control. For more precise control, use
+the vKill packet (@pxref{vKill packet}).
+
+If the target system immediately closes the connection in response to
+@samp{k}, @value{GDBN} does not consider the lack of packet
+acknowledgment to be an error, and assumes the kill was successful.
+
+If connected using @kbd{target extended-remote}, and the target does
+not close the connection in response to a kill request, @value{GDBN}
+probes the target state as if a new connection was opened
+(@pxref{? packet}).
@item m @var{addr},@var{length}
@cindex @samp{m} packet
@@ -34258,6 +34275,7 @@ request is completed.
@item vKill;@var{pid}
@cindex @samp{vKill} packet
+@anchor{vKill packet}
Kill the process with the specified process ID. @var{pid} is a
hexadecimal integer identifying the process. This packet is used in
preference to @samp{k} when multiprocess protocol extensions are