Fix typo in vFile:pwrite documentation

A user on irc noticed that the remote protocol documentation mentioned
"vFile:write" -- but this is a typo, there is only "vFile:pwrite".
This patch fixes the bug.  Tested by rebuilding, committing as
obvious.

gdb/doc/ChangeLog
2019-11-11  Tom Tromey  <tromey@adacore.com>

	* gdb.texinfo (Host I/O Packets): Fix typo in "vFile:pwrite".

Change-Id: I2f668a691eed7883ba6bc092471739f44c82301b

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index fec0ebd8a1126a51009d6f7ca09e5ad571ff7fa6..dcce6fad5e2436676f93d478989ced1bae741342 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2019-11-11  Tom Tromey  <tromey@adacore.com>
+
+       * gdb.texinfo (Host I/O Packets): Fix typo in "vFile:pwrite".
+
 2019-11-10  Andrew Burgess  <andrew.burgess@embecosm.com>
 
        * python.texi (Symbols In Python): Add documentation for

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 70e4be1524402a02a82cadce92fdae2076fb9bce..e702b29ee17915bb10f6775029b0a1f4e228b85a 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -41773,7 +41773,7 @@ Write @var{data} (a binary buffer) to the open file corresponding
 to @var{fd}.  Start the write at @var{offset} from the start of the
 file.  Unlike many @code{write} system calls, there is no
 separate @var{count} argument; the length of @var{data} in the
-packet is used.  @samp{vFile:write} returns the number of bytes written,
+packet is used.  @samp{vFile:pwrite} returns the number of bytes written,
 which may be shorter than the length of @var{data}, or -1 if an
 error occurred.