[PATCH] Document short responses to qXfer:object:read.

David Taylor
2016-05-26T18:11:07Z

[We have a copyright assignment on file (in case it matters -- but, this
is short enough that I doubt it is is copyrightable).]

This is a follow up to my May 9th posting (subject: qXfer:threads:read
packets) on the gdb mailing list. This only addresses the short
response part, not the dtd vs documentation discrepancy.

gdb/doc/ChangeLog | 5 +++++
gdb/doc/gdb.texinfo | 5 +++++
2 files changed, 10 insertions(+)

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 34b9527..b46075f 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2016-05-26 David Taylor <dtaylor@emc.com>
+
+ * gdb.texinfo (General Query Packets): Document treatment of short
+ qXfer responses and EOF indication.
+
2016-05-23 Tom Tromey <tom@tromey.com>

* python.texi (Basic Python): Document gdb.breakpoints return.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 8f1ad4e..c674c7a 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -37251,6 +37251,11 @@ starting at @var{offset} bytes into the data. The content and
encoding of @var{annex} is specific to @var{object}; it can supply
additional details about what data to access.

+The target is permitted to return a short response. The response is
+considered to cover the range @var{offset} (inclusive) to @var{offset}
++ @var{response length} (exclusive). End of file is indicated by a
+zero length response.
+
Here are the specific requests of this form defined so far. All
@samp{qXfer:@var{object}:read:@dots{}} requests use the same reply
formats, listed below.
--
1.9.1