From: Eli Zaretskii <eliz@gnu.org>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org, palves@redhat.com,
jan.kratochvil@redhat.com, fercerpav@gmail.com,
sekiriki@gmail.com
Subject: Re: [PATCH] Implement IPv6 support for GDB/gdbserver
Date: Wed, 23 May 2018 23:40:00 -0000 [thread overview]
Message-ID: <8336yich5s.fsf@gnu.org> (raw)
In-Reply-To: <20180523185719.22832-1-sergiodj@redhat.com> (message from Sergio Durigan Junior on Wed, 23 May 2018 14:57:19 -0400)
> From: Sergio Durigan Junior <sergiodj@redhat.com>
> Cc: Pedro Alves <palves@redhat.com>,
> Eli Zaretskii <eliz@gnu.org>,
> Jan Kratochvil <jan.kratochvil@redhat.com>,
> Paul Fertser <fercerpav@gmail.com>,
> Tsutomu Seki <sekiriki@gmail.com>,
> Sergio Durigan Junior <sergiodj@redhat.com>
> Date: Wed, 23 May 2018 14:57:19 -0400
>
> gdb/ChangeLog:
> yyyy-mm-dd Sergio Durigan Junior <sergiodj@redhat.com>
> Jan Kratochvil <jan.kratochvil@redhat.com>
> Paul Fertser <fercerpav@gmail.com>
> Tsutomu Seki <sekiriki@gmail.com>
>
> * Makefile.in (COMMON_SFILES): Add 'common/netstuff.c'.
> (HFILES_NO_SRCDIR): Add 'common/netstuff.h'.
> * NEWS (Changes since GDB 8.1): Mention IPv6 support.
> * common/netstuff.c: New file.
> * common/netstuff.h: New file.
> * ser-tcp.c: Include 'netstuff.h' and 'wspiapi.h'.
> (net_open): Handle IPv6-style hostnames; implement support for
> IPv6 connections.
>
> gdb/gdbserver/ChangeLog:
> yyyy-mm-dd Sergio Durigan Junior <sergiodj@redhat.com>
> Jan Kratochvil <jan.kratochvil@redhat.com>
> Paul Fertser <fercerpav@gmail.com>
> Tsutomu Seki <sekiriki@gmail.com>
>
> * Makefile.in (SFILES): Add '$(srcdir)/common/netstuff.c'.
> (OBS): Add 'common/netstuff.o'.
> * gdbreplay.c: Include 'wspiapi.h'.
> (remote_open): Implement support for IPv6
> connections.
> * remote-utils.c: Include 'netstuff.h', 'filestuff.h'
> and 'wspiapi.h'.
> (handle_accept_event): Accept connections from IPv6 sources.
> (remote_prepare): Handle IPv6-style hostnames; implement
> support for IPv6 connections.
> (remote_open): Implement support for printing connections from
> IPv6 sources.
>
> gdb/testsuite/ChangeLog:
> yyyy-mm-dd Sergio Durigan Junior <sergiodj@redhat.com>
> Jan Kratochvil <jan.kratochvil@redhat.com>
> Paul Fertser <fercerpav@gmail.com>
> Tsutomu Seki <sekiriki@gmail.com>
>
> * README (Testsuite Parameters): Mention new 'GDB_TEST_IPV6'
> parameter.
> * boards/gdbserver-base.exp (get_comm_port_localhost_ipv6):
> New procedure.
> * boards/native-extended-gdbserver.exp: Detect 'GDB_TEST_IPV6'
> and change board info accordingly.
> * boards/native-gdbserver.exp: Likewise.
> * gdb.server/run-without-local-binary.exp: Improve regexp used
> for detecting when a remote debugging connection succeeds.
>
> gdb/doc/ChangeLog:
> yyyy-mm-dd Sergio Durigan Junior <sergiodj@redhat.com>
> Jan Kratochvil <jan.kratochvil@redhat.com>
> Paul Fertser <fercerpav@gmail.com>
> Tsutomu Seki <sekiriki@gmail.com>
>
> * gdb.texinfo (Remote Connection Commands): Add explanation
> about new IPv6 support. Add new connection prefixes.
The documentation parts are approved, with a couple of minor comments:
> @item target remote @code{@var{host}:@var{port}}
> +@itemx target remote @code{@var{@r{[}host@r{]}}:@var{port}}
Isn't having 2 lines here redundant? If the HOST part is optional,
the second line already covers the first, right?
Similarly with other forms of this command.
> @item target remote @code{udp:@var{host}:@var{port}}
> +@itemx target remote @code{udp:@var{host}:@var{port}}
And here these two lines are exactly identical, right?
> +To connect to port 2828 on a terminal server whose address is
> +@code{2001::f8ff::67cf}, you can either use the square bracket syntax:
> +
> +@smallexample
> +target remote [2001::f8ff::67cf]:2828
> +@end smallexample
> +
> +Or explicitly specify the @acronym{IPv6} protocol:
The last sentence is actually a continuation of the one before the
example. So it should start with a lower-case letter, and please
insert a @noindent (on its own line) before that, to prevent Texnfo
processors from indenting that line.
Thanks.
next prev parent reply other threads:[~2018-05-23 19:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 21:48 Sergio Durigan Junior
2018-05-23 23:40 ` Eli Zaretskii [this message]
2018-05-24 0:41 ` Sergio Durigan Junior
2018-05-24 16:54 ` Eli Zaretskii
2018-05-25 1:57 ` Sergio Durigan Junior
2018-05-31 20:10 ` Sergio Durigan Junior
2018-06-06 12:26 ` Pedro Alves
2018-06-08 1:13 ` Sergio Durigan Junior
2018-06-08 13:53 ` Pedro Alves
2018-06-08 17:47 ` Sergio Durigan Junior
2018-06-08 18:44 ` Pedro Alves
2018-06-08 19:28 ` Pedro Alves
2018-06-08 19:51 ` Pedro Alves
2018-06-08 20:43 ` Sergio Durigan Junior
2018-06-08 21:21 ` Sergio Durigan Junior
2018-06-08 21:51 ` Pedro Alves
2018-06-08 22:01 ` Sergio Durigan Junior
2018-06-15 0:25 ` [PATCH v2] " Sergio Durigan Junior
2018-06-15 7:12 ` Eli Zaretskii
2018-06-20 15:24 ` Pedro Alves
2018-06-21 4:54 ` Sergio Durigan Junior
2018-07-07 20:47 ` [PATCH v3] " Sergio Durigan Junior
2018-07-11 12:55 ` Pedro Alves
2018-07-11 19:13 ` Sergio Durigan Junior
2018-07-11 19:16 ` [PATCH v4] " Sergio Durigan Junior
2018-07-11 21:48 ` Pedro Alves
2018-07-11 23:43 ` Sergio Durigan Junior
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=8336yich5s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=fercerpav@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=sekiriki@gmail.com \
--cc=sergiodj@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).