[PATCH] doc: gdbserver allows for subsequent and not for additional connections.

Sanimir Agovic
2013-08-05T09:24:33Z

Reading the gdb documentation about TCP port allocation lifecycle I had the
impression that gdbserver allows multiple connection, which it does not. Thus
the term "subsequent" suites better than "additional".

old> By default, gdbserver keeps the listening TCP port open, so that
additional connections are possible.
^^^^^^^^^^

new> By default, gdbserver keeps the listening TCP port open, so that
subsequent connections are possible.
^^^^^^^^^^

-Sanimir

doc/

2013-08-05 Sanimir Agovic <sanimir.agovic@intel.com>

* gdb.texinfo (TCP port allocation lifecycle): Gdbserver by default
allows for subsequent and not for additional connections.

---
gdb/doc/gdb.texinfo | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index cb393e8..6d5dec4 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -18182,7 +18182,7 @@ completeness, at most one @value{GDBN} can be connected at a time.

@cindex @option{--once}, @code{gdbserver} option
By default, @code{gdbserver} keeps the listening TCP port open, so that
-additional connections are possible. However, if you start @code{gdbserver}
+subsequent connections are possible. However, if you start @code{gdbserver}
with the @option{--once} option, it will stop listening for any further
connection attempts after connecting to the first @value{GDBN} session. This
means no further connections to @code{gdbserver} will be possible after the
--
1.7.1.1