* [PATCH] doc: gdbserver allows for subsequent and not for additional connections.
@ 2013-08-05 9:24 Sanimir Agovic
2013-08-05 14:54 ` Eli Zaretskii
0 siblings, 1 reply; 6+ messages in thread
From: Sanimir Agovic @ 2013-08-05 9:24 UTC (permalink / raw)
To: eliz; +Cc: gdb-patches
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH] doc: gdbserver allows for subsequent and not for additional connections.
2013-08-05 9:24 [PATCH] doc: gdbserver allows for subsequent and not for additional connections Sanimir Agovic
@ 2013-08-05 14:54 ` Eli Zaretskii
2013-08-05 15:00 ` Agovic, Sanimir
0 siblings, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2013-08-05 14:54 UTC (permalink / raw)
To: Sanimir Agovic; +Cc: gdb-patches
> 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: [PATCH] doc: gdbserver allows for subsequent and not for additional connections.
2013-08-05 14:54 ` Eli Zaretskii
@ 2013-08-05 15:00 ` Agovic, Sanimir
2013-08-05 15:06 ` Tom Tromey
0 siblings, 1 reply; 6+ messages in thread
From: Agovic, Sanimir @ 2013-08-05 15:00 UTC (permalink / raw)
To: 'Eli Zaretskii'; +Cc: gdb-patches
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-owner@sourceware.org] On Behalf
> Of Eli Zaretskii
> Sent: Monday, August 05, 2013 04:54 PM
> > 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.
>
Well, I agree that it might be personal taste, hence I will drop the patch.
Thanks for the feedback.
-Sanimir
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] doc: gdbserver allows for subsequent and not for additional connections.
2013-08-05 15:00 ` Agovic, Sanimir
@ 2013-08-05 15:06 ` Tom Tromey
2013-08-05 15:20 ` Eli Zaretskii
0 siblings, 1 reply; 6+ messages in thread
From: Tom Tromey @ 2013-08-05 15:06 UTC (permalink / raw)
To: Agovic, Sanimir; +Cc: 'Eli Zaretskii', gdb-patches
>> > 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.
>> > ^^^^^^^^^^
Eli> Is it really such a significant difference? I'm not sure.
Sanimir> Well, I agree that it might be personal taste, hence I will
Sanimir> drop the patch.
I think it is an improvement.
I think "additional" here implies multiple simultaneous connections --
in fact, what confused you in the first place. "Subsequent" makes this
differentiation clear.
Tom
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] doc: gdbserver allows for subsequent and not for additional connections.
2013-08-05 15:06 ` Tom Tromey
@ 2013-08-05 15:20 ` Eli Zaretskii
2013-08-05 15:40 ` Agovic, Sanimir
0 siblings, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2013-08-05 15:20 UTC (permalink / raw)
To: Tom Tromey; +Cc: sanimir.agovic, gdb-patches
> From: Tom Tromey <tromey@redhat.com>
> Cc: "'Eli Zaretskii'" <eliz@gnu.org>,
> "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
> Date: Mon, 05 Aug 2013 09:06:00 -0600
>
> >> > 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.
> >> > ^^^^^^^^^^
>
> Eli> Is it really such a significant difference? I'm not sure.
>
> Sanimir> Well, I agree that it might be personal taste, hence I will
> Sanimir> drop the patch.
>
> I think it is an improvement.
>
> I think "additional" here implies multiple simultaneous connections --
> in fact, what confused you in the first place. "Subsequent" makes this
> differentiation clear.
Fine with me, feel free to install.
Thanks.
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: [PATCH] doc: gdbserver allows for subsequent and not for additional connections.
2013-08-05 15:20 ` Eli Zaretskii
@ 2013-08-05 15:40 ` Agovic, Sanimir
0 siblings, 0 replies; 6+ messages in thread
From: Agovic, Sanimir @ 2013-08-05 15:40 UTC (permalink / raw)
To: 'Eli Zaretskii', Tom Tromey; +Cc: gdb-patches
Thanks, committed. Rephrased brief commit message to:
"gdbserver allows for subsequent and not for multiple simultaneous connections."
-Sanimir
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-owner@sourceware.org] On Behalf
> Of Eli Zaretskii
> Sent: Monday, August 05, 2013 05:20 PM
> To: Tom Tromey
> Cc: Agovic, Sanimir; gdb-patches@sourceware.org
> Subject: Re: [PATCH] doc: gdbserver allows for subsequent and not for additional
> connections.
>
> > From: Tom Tromey <tromey@redhat.com>
> > Cc: "'Eli Zaretskii'" <eliz@gnu.org>,
> > "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
> > Date: Mon, 05 Aug 2013 09:06:00 -0600
> >
> > >> > 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.
> > >> > ^^^^^^^^^^
> >
> > Eli> Is it really such a significant difference? I'm not sure.
> >
> > Sanimir> Well, I agree that it might be personal taste, hence I will
> > Sanimir> drop the patch.
> >
> > I think it is an improvement.
> >
> > I think "additional" here implies multiple simultaneous connections --
> > in fact, what confused you in the first place. "Subsequent" makes this
> > differentiation clear.
>
> Fine with me, feel free to install.
>
> Thanks.
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-08-05 15:40 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-05 9:24 [PATCH] doc: gdbserver allows for subsequent and not for additional connections Sanimir Agovic
2013-08-05 14:54 ` Eli Zaretskii
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox