From: Eli Zaretskii <eliz@gnu.org>
To: Sanimir Agovic <sanimir.agovic@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] doc: gdbserver allows for subsequent and not for additional connections.
Date: Mon, 05 Aug 2013 14:54:00 -0000 [thread overview]
Message-ID: <83txj4w5m7.fsf@gnu.org> (raw)
In-Reply-To: <1375694633-30275-1-git-send-email-sanimir.agovic@intel.com>
> From: Sanimir Agovic <sanimir.agovic@intel.com>
> Cc: gdb-patches@sourceware.org
> Date: Mon, 5 Aug 2013 11:23:53 +0200
>
> 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.
> ^^^^^^^^^^
Is it really such a significant difference? I'm not sure.
Thanks.
next prev parent reply other threads:[~2013-08-05 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 9:24 Sanimir Agovic
2013-08-05 14:54 ` Eli Zaretskii [this message]
2013-08-05 15:00 ` Agovic, Sanimir
2013-08-05 15:06 ` Tom Tromey
2013-08-05 15:20 ` Eli Zaretskii
2013-08-05 15:40 ` Agovic, Sanimir
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=83txj4w5m7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sanimir.agovic@intel.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