public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] Fix non-existent "@var{thread-id}" in stop reply descriptions
@ 2022-07-11 17:18 Pedro Alves
0 siblings, 0 replies; only message in thread
From: Pedro Alves @ 2022-07-11 17:18 UTC (permalink / raw)
To: gdb-cvs
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=fdee9814e6878311671b2ad57d7e2e03d3ceab9a
commit fdee9814e6878311671b2ad57d7e2e03d3ceab9a
Author: Pedro Alves <pedro@palves.net>
Date: Mon Jul 11 16:05:00 2022 +0100
Fix non-existent "@var{thread-id}" in stop reply descriptions
In the description of stop replies, where the "thread" register is
explained, and where the fork and vfork stop reasons are detailed,
there are references to "@var{thread-id}", but such variable does not
actually exist. This commit fixes it.
Change-Id: If679944aaf15f6f64aabe506339a9e7667864cab
Diff:
---
gdb/doc/gdb.texinfo | 20 +++++++++-----------
1 file changed, 9 insertions(+), 11 deletions(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 86394f631ac..562e4c1f628 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -41672,7 +41672,7 @@ series of bytes in target byte order, with each byte given by a
two-digit hex number.
@item
-If @var{n} is @samp{thread}, then @var{r} is the @var{thread-id} of
+If @var{n} is @samp{thread}, then @var{r} is the thread ID of
the stopped thread, as specified in @ref{thread-id syntax}.
@item
@@ -41749,11 +41749,10 @@ apply.
@cindex fork events, remote reply
@item fork
-The packet indicates that @code{fork} was called, and @var{r}
-is the thread ID of the new child process. Refer to
-@ref{thread-id syntax} for the format of the @var{thread-id}
-field. This packet is only applicable to targets that support
-fork events.
+The packet indicates that @code{fork} was called, and @var{r} is the
+thread ID of the new child process, as specified in @ref{thread-id
+syntax}. This packet is only applicable to targets that support fork
+events.
This packet should not be sent by default; older @value{GDBN} versions
did not support it. @value{GDBN} requests it, by supplying an
@@ -41763,11 +41762,10 @@ indicating support.
@cindex vfork events, remote reply
@item vfork
-The packet indicates that @code{vfork} was called, and @var{r}
-is the thread ID of the new child process. Refer to
-@ref{thread-id syntax} for the format of the @var{thread-id}
-field. This packet is only applicable to targets that support
-vfork events.
+The packet indicates that @code{vfork} was called, and @var{r} is the
+thread ID of the new child process, as specified in @ref{thread-id
+syntax}. This packet is only applicable to targets that support vfork
+events.
This packet should not be sent by default; older @value{GDBN} versions
did not support it. @value{GDBN} requests it, by supplying an
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-07-11 17:18 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-11 17:18 [binutils-gdb] Fix non-existent "@var{thread-id}" in stop reply descriptions Pedro Alves
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).