From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 1551) id 4D63B385842F; Mon, 11 Jul 2022 17:18:55 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4D63B385842F Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable From: Pedro Alves To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Fix non-existent "@var{thread-id}" in stop reply descriptions X-Act-Checkin: binutils-gdb X-Git-Author: Pedro Alves X-Git-Refname: refs/heads/master X-Git-Oldrev: f58d9432cdf8a279ed584efdb9791f44bb4dcd9e X-Git-Newrev: fdee9814e6878311671b2ad57d7e2e03d3ceab9a Message-Id: <20220711171855.4D63B385842F@sourceware.org> Date: Mon, 11 Jul 2022 17:18:55 +0000 (GMT) X-BeenThere: gdb-cvs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-cvs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2022 17:18:55 -0000 https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3Dfdee9814e687= 8311671b2ad57d7e2e03d3ceab9a commit fdee9814e6878311671b2ad57d7e2e03d3ceab9a Author: Pedro Alves Date: Mon Jul 11 16:05:00 2022 +0100 Fix non-existent "@var{thread-id}" in stop reply descriptions =20 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. =20 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 byt= e given by a two-digit hex number. =20 @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}. =20 @item @@ -41749,11 +41749,10 @@ apply. =20 @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. =20 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. =20 @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. =20 This packet should not be sent by default; older @value{GDBN} versions did not support it. @value{GDBN} requests it, by supplying an