From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4834 invoked by alias); 5 Aug 2013 09:24:33 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 4824 invoked by uid 89); 5 Aug 2013 09:24:33 -0000 X-Spam-SWARE-Status: No, score=-4.0 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RDNS_NONE,TO_NO_BRKTS_NORDNS autolearn=no version=3.3.1 Received: from Unknown (HELO mga02.intel.com) (134.134.136.20) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 05 Aug 2013 09:24:32 +0000 Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 05 Aug 2013 02:24:12 -0700 X-ExtLoop1: 1 Received: from irvmail001.ir.intel.com ([163.33.26.43]) by orsmga001.jf.intel.com with ESMTP; 05 Aug 2013 02:24:01 -0700 Received: from ulliclel004.iul.intel.com (ulliclel004.iul.intel.com [172.28.50.125]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id r759O0Ab019047; Mon, 5 Aug 2013 10:24:00 +0100 Received: from ulliclel004.iul.intel.com (ulliclel004.iul.intel.com [127.0.0.1]) by ulliclel004.iul.intel.com (8.13.8/8.12.8/MailSET/client) with ESMTP id r759Nx9v030308; Mon, 5 Aug 2013 11:23:59 +0200 Received: (from sagovic@localhost) by ulliclel004.iul.intel.com (8.13.8/8.13.1/Submit) id r759NrCg030307; Mon, 5 Aug 2013 11:23:53 +0200 From: Sanimir Agovic To: eliz@gnu.org Cc: gdb-patches@sourceware.org Subject: [PATCH] doc: gdbserver allows for subsequent and not for additional connections. Date: Mon, 05 Aug 2013 09:24:00 -0000 Message-Id: <1375694633-30275-1-git-send-email-sanimir.agovic@intel.com> X-SW-Source: 2013-08/txt/msg00132.txt.bz2 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 * 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