From: Tankut Baris Aktemur Date: Tue, 14 Jan 2025 09:10:29 +0000 (+0100) Subject: gdb, doc: mention the 'S' option for the QTDP packet X-Git-Tag: binutils-2_44~158 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e68a45754c826032d091434dac5c03680e579bb5;p=thirdparty%2Fbinutils-gdb.git gdb, doc: mention the 'S' option for the QTDP packet I noticed that gdbserver accepts an 'S' option for the QTDP packet to create a static tracepoint, but this is not mentioned in the document. Update the document. I first thought about updating the argument as `[:Flen|:S]`, but then opted for `[:Flen][:S]`. Although it is odd that ':F' and ':S' are allowed to co-exist, the implementation at the gdbserver side allows this and handles the packet arguments so that the right-most positioned ':F' or ':S' overwrites the final tracepoint type. When the documentation is missing, the implementation usually determines the behavior. Reviewed-By: Eli Zaretskii --- diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 73b6c59278d..553a002dd33 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -46002,7 +46002,7 @@ tracepoints (@pxref{Tracepoints}). @table @samp -@item QTDP:@var{n}:@var{addr}:@var{ena}:@var{step}:@var{pass}[:F@var{flen}][:X@var{len},@var{bytes}]@r{[}-@r{]} +@item QTDP:@var{n}:@var{addr}:@var{ena}:@var{step}:@var{pass}[:F@var{flen}][:S][:X@var{len},@var{bytes}]@r{[}-@r{]} @cindex @samp{QTDP} packet Create a new tracepoint, number @var{n}, at @var{addr}. If @var{ena} is @samp{E}, then the tracepoint is enabled; if it is @samp{D}, then @@ -46010,7 +46010,8 @@ the tracepoint is disabled. The @var{step} gives the tracepoint's step count, and @var{pass} gives its pass count. If an @samp{F} is present, then the tracepoint is to be a fast tracepoint, and the @var{flen} is the number of bytes that the target should copy elsewhere to make room -for the tracepoint. If an @samp{X} is present, it introduces a +for the tracepoint. If an @samp{S} is present, the tracepoint is to be +a static tracepoint. If an @samp{X} is present, it introduces a tracepoint condition, which consists of a hexadecimal length, followed by a comma and hex-encoded bytes, in a manner similar to action encodings as described below. If the trailing @samp{-} is present,