From: Eli Zaretskii <eliz@gnu.org>
To: Tsutomu Seki <sekiriki@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] supports IPv6 only remote target
Date: Tue, 09 Feb 2016 17:29:00 -0000 [thread overview]
Message-ID: <831t8ldc80.fsf@gnu.org> (raw)
In-Reply-To: <CALZjo7uhLO0V9HPhW7wn-N5fs2dgwc4n7Gm2e20dezQL29_kgA@mail.gmail.com> (message from Tsutomu Seki on Tue, 9 Feb 2016 22:49:57 +0900)
> Date: Tue, 9 Feb 2016 22:49:57 +0900
> From: Tsutomu Seki <sekiriki@gmail.com>
>
> +Numerical @acronym{IPv6} address must be enclosed in square brackets.
> +For example, to connect to port 2159 of a target which has IPv6
> +link-local address fe80::1 on eth1:
Please use @code with the address string fe80::1.
> +
> +@smallexample
> +target remote [fe80::1%eth1]:2159
> +@end smallexample
This example seems to imply that more than just taking brackets is
required. Should we tell more about that?
> +The service name is default to ``gdbremote''. If the service name is
Please use
The service name defaults to @code{"gdbremote"}
Also, we leave 2 spaces between sentences.
> +present in service list (e.g.@: @file{/etc/services} on @sc{gnu}/Linux
> +systems), and target is listening on assigned port, you can omit the
I guess you mean "on the port assigned to that service", yes?
The documentation parts are OK with these fixed.
> --- a/gdb/ser-tcp.c
> +++ b/gdb/ser-tcp.c
> @@ -39,6 +39,7 @@
>
> #ifdef USE_WIN32API
> #include <winsock2.h>
> +#include <wspiapi.h>
I think this will break the build with mingw.org's MinGW. It doesn't
have wspiapi.h, AFAIK. What exactly is needed from that header?
Thanks.
next prev parent reply other threads:[~2016-02-09 17:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 13:50 Tsutomu Seki
2016-02-09 17:29 ` Eli Zaretskii [this message]
2016-02-10 11:43 ` Tsutomu Seki
2016-02-10 18:14 ` Eli Zaretskii
2016-02-10 18:55 ` Tsutomu Seki
2016-02-10 19:22 ` Eli Zaretskii
[not found] ` <56E1A467.5060509@redhat.com>
2016-03-10 21:20 ` Paul Fertser
2016-03-11 1:42 ` Tsutomu Seki
2016-03-11 10:25 ` Pedro Alves
2018-04-10 19:21 ` Sergio Durigan Junior
2018-04-10 20:05 ` Paul Fertser
2018-04-11 2:26 ` Eli Zaretskii
2018-04-11 12:19 ` Tsutomu Seki
2018-04-11 16:18 ` Sergio Durigan Junior
2016-03-11 15:52 ` Eli Zaretskii
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=831t8ldc80.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sekiriki@gmail.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