From: "Marcin Kościelnicki" <koriakin@0x04.net>
To: palves@redhat.com
Cc: gdb-patches@sourceware.org, "Marcin Kościelnicki" <koriakin@0x04.net>
Subject: [PATCH 3/3] gdb/doc: Add documentation for tfile description section lines.
Date: Wed, 10 Feb 2016 20:19:00 -0000 [thread overview]
Message-ID: <1455135588-21970-1-git-send-email-koriakin@0x04.net> (raw)
In-Reply-To: <56BB482A.1060307@redhat.com>
gdb/doc/ChangeLog:
* gdb.texinfo (Trace File Format): Add documentation for description
section lines.
---
Here's the promised documentation for tdesc lines and then some.
gdb/doc/ChangeLog | 5 +++++
gdb/doc/gdb.texinfo | 33 ++++++++++++++++++++++++++++++++-
2 files changed, 37 insertions(+), 1 deletion(-)
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 75b24ef..12ace48 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,5 +1,10 @@
2016-02-10 Marcin KoÅcielnicki <koriakin@0x04.net>
+ * gdb.texinfo (Trace File Format): Add documentation for description
+ section lines.
+
+2016-02-10 Marcin KoÅcielnicki <koriakin@0x04.net>
+
* gdb.texinfo (Trace File Format): Remove misleading information
about register block ordering.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 9db234e..0028eda 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -41031,7 +41031,38 @@ as tracepoint definitions or register set size. @value{GDBN} will
ignore any line that it does not recognize. An empty line marks the end
of this section.
-@c FIXME add some specific types of data
+@table @code
+@item R @var{size}
+Specifies the size of a register block in bytes. This is equal to the
+size of a @code{g} packet payload in the remote protocol. @var{size}
+is an ascii decimal number. There should be only one such line in
+a single trace file.
+
+@item status @var{status}
+Trace status. @var{status} has the same format as a @code{qTStatus}
+remote packet reply. There should be only one such line in a single trace
+file.
+
+@item tp @var{payload}
+Tracepoint definition. The @var{payload} has the same format as
+@code{qTfP}/@code{qTsP} remote packet reply payload. A single tracepoint
+may take multiple lines of definition, corresponding to the multiple
+reply packets.
+
+@item tsv @var{payload}
+Trace state variable definition. The @var{payload} has the same format as
+@code{qTfV}/@code{qTsV} remote packet reply payload. A single variable
+may take multiple lines of definition, corresponding to the multiple
+reply packets.
+
+@item tdesc @var{payload}
+Target description in XML format. The @var{payload} is a single line of
+the XML file. All such lines should be concatenated together to get
+the original XML file. This file is in the same format as @code{qXfer}
+@code{features} payload, and corresponds to the main @code{target.xml}
+file. Includes are not allowed.
+
+@end table
The trace frame section consists of a number of consecutive frames.
Each frame begins with a two-byte tracepoint number, followed by a
--
2.7.0
next prev parent reply other threads:[~2016-02-10 20:19 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 15:39 [PATCH 0/4] Save target description in tfile Marcin Kościelnicki
2016-02-06 15:39 ` [PATCH 2/4] gdb.trace: Read XML target description from tfile Marcin Kościelnicki
2016-02-10 13:02 ` Pedro Alves
2016-02-10 20:19 ` [PATCH 2/3] " Marcin Kościelnicki
2016-02-10 22:20 ` Pedro Alves
2016-02-10 22:35 ` Marcin Kościelnicki
2016-02-06 15:39 ` [PATCH 3/4] gdb.trace: Use g packet order in tfile_fetch_registers Marcin Kościelnicki
2016-02-10 13:20 ` Pedro Alves
2016-02-10 13:21 ` Marcin Kościelnicki
2016-02-10 13:54 ` Pedro Alves
2016-02-10 14:12 ` [PATCH] " Marcin Kościelnicki
2016-02-10 14:21 ` Pedro Alves
2016-02-10 14:49 ` Marcin Kościelnicki
2016-02-06 15:39 ` [PATCH 1/4] gdb.trace: Save XML target description in tfile Marcin Kościelnicki
2016-02-10 13:02 ` Pedro Alves
2016-02-10 20:18 ` [PATCH 1/3] " Marcin Kościelnicki
2016-02-10 22:20 ` Pedro Alves
2016-02-10 22:35 ` Marcin Kościelnicki
2016-02-11 19:02 ` Simon Marchi
2016-02-11 21:28 ` Sergio Durigan Junior
2016-02-11 22:31 ` Marcin Kościelnicki
2016-02-11 22:56 ` [PATCH] gdb: Fix build failure in xml-tdesc.c without expat Marcin Kościelnicki
2016-02-12 10:06 ` Pedro Alves
2016-02-12 10:10 ` Marcin Kościelnicki
2016-02-12 10:19 ` Pedro Alves
2016-02-12 10:21 ` Marcin Kościelnicki
2016-02-06 15:47 ` [PATCH 4/4] gdb.trace: Fix off-by-one in tfile_fetch_registers Marcin Kościelnicki
2016-02-10 13:22 ` Pedro Alves
2016-02-10 13:53 ` Marcin Kościelnicki
2016-02-06 20:54 ` [PATCH 5/6] gdb/x86: Implement ax_pseudo_register_collect hook Marcin Kościelnicki
2016-02-06 20:54 ` [PATCH 6/6] gdb.trace: Add a testcase for tdesc in tfile Marcin Kościelnicki
2016-02-10 13:50 ` Pedro Alves
2016-02-11 10:14 ` [PATCH] " Marcin Kościelnicki
2016-02-11 13:00 ` Pedro Alves
2016-02-11 14:17 ` Marcin Kościelnicki
2016-02-12 18:32 ` Antoine Tremblay
2016-02-12 18:40 ` Marcin Kościelnicki
2016-02-12 18:49 ` Antoine Tremblay
2016-02-12 18:53 ` Marcin Kościelnicki
2016-02-12 18:57 ` Antoine Tremblay
2016-02-12 19:47 ` [PATCH] gdb.trace/tfile-avx.c: Change ymm15 to xmm15 for old gcc Marcin Kościelnicki
2016-02-12 19:57 ` Pedro Alves
2016-02-12 21:34 ` Marcin Kościelnicki
2016-02-10 13:31 ` [PATCH 5/6] gdb/x86: Implement ax_pseudo_register_collect hook Pedro Alves
2016-02-10 13:34 ` Marcin Kościelnicki
2016-02-10 13:50 ` Pedro Alves
2016-02-10 14:27 ` [PATCH] " Marcin Kościelnicki
2016-02-10 14:28 ` Pedro Alves
2016-02-10 14:49 ` Marcin Kościelnicki
2016-02-10 14:24 ` [PATCH 0/4] Save target description in tfile Pedro Alves
2016-02-10 14:25 ` Marcin Kościelnicki
2016-02-10 20:19 ` Marcin Kościelnicki [this message]
2016-02-10 22:20 ` [PATCH 3/3] gdb/doc: Add documentation for tfile description section lines Pedro Alves
2016-02-17 9:50 ` Marcin Kościelnicki
2016-02-17 15:37 ` Pedro Alves
2016-02-17 15:38 ` Pedro Alves
2016-02-17 15:59 ` Eli Zaretskii
2016-02-17 16:04 ` Marcin Kościelnicki
2016-02-17 16:05 ` Pedro Alves
2016-02-18 8:28 ` Marcin Kościelnicki
2016-02-11 17:36 ` [PATCH 0/4] Save target description in tfile Yao Qi
2016-02-12 1:49 ` Marcin Kościelnicki
2016-02-12 12:13 ` Yao Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1455135588-21970-1-git-send-email-koriakin@0x04.net \
--to=koriakin@0x04.net \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox