aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc/gdb.texinfo
diff options
context:
space:
mode:
authorTankut Baris Aktemur <tankut.baris.aktemur@intel.com>2025-01-14 10:10:29 +0100
committerTankut Baris Aktemur <tankut.baris.aktemur@intel.com>2025-01-14 10:27:57 +0100
commite68a45754c826032d091434dac5c03680e579bb5 (patch)
tree9e1b7a45deb1302d0333214956e72fcd3092ea5d /gdb/doc/gdb.texinfo
parent6ac02727dc9fd1f4b505a4e8cca30b6c75bd4899 (diff)
downloadgdb-e68a45754c826032d091434dac5c03680e579bb5.zip
gdb-e68a45754c826032d091434dac5c03680e579bb5.tar.gz
gdb-e68a45754c826032d091434dac5c03680e579bb5.tar.bz2
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 <eliz@gnu.org>
Diffstat (limited to 'gdb/doc/gdb.texinfo')
-rw-r--r--gdb/doc/gdb.texinfo5
1 files changed, 3 insertions, 2 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 73b6c59..553a002 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,