From: Christopher Faylor <me@cgf.cx>
To: Mark Mitchell <mark@codesourcery.com>, gdb-patches@sources.redhat.com
Subject: Re: PATCH: Windows sockets
Date: Sat, 26 Mar 2005 02:09:00 -0000 [thread overview]
Message-ID: <20050326020850.GA19864@trixie.casa.cgf.cx> (raw)
In-Reply-To: <200503260127.j2Q1R59a022152@sethra.codesourcery.com>
On Fri, Mar 25, 2005 at 05:27:05PM -0800, Mark Mitchell wrote:
>Here's the first "interesting" patch for Windows support. This patch
>modifies ser-tcp.c to support Windows, so that we can use a GDB
>running on Windows to talk to a gdbserver process.
>
>Here is a sumary of the changes in this patch:
>
>1. Link with -lws2_32 on MinGW so we can use sockets.
>
>2. In defs.h, define WINAPI so that source files know whether they are
> supposed to use the Windows API.
>
>3. Move ser_unix_readchar and friends (which were only barely
> UNIX-specific) into ser-base.c, renaming appropriately.
>
>4. Add a new member (read_prim) to struct serial_ops, and use it from
> ser_base_readchar. The reason for this is that sockets must be
> read with "recv" on Windows; plain "read" does not work. So, we
> need a way to indicate which low-level primitive to use to read
> from a file descriptor.
>
>5. Make a handful of minor changes to ter-tcp.c to account for
> differences in the BSD and Windows sockets APIs.
>
>6. Tweak safe_strerror to deal with Windows sockets error codes.
>
>Tested on x86_64-unknown-linux-gnu, to make sure I didn't break UNIX,
>and cursorily on Windows (with other patches, not yet submitted).
>
>OK to apply?
The windows-specific configury parts look ok to me. That's all I
can approve, although the other bits look right too.
cgf
next prev parent reply other threads:[~2005-03-26 2:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 1:27 Mark Mitchell
2005-03-26 2:09 ` Christopher Faylor [this message]
2005-03-26 8:47 ` Mark Kettenis
2005-03-26 17:38 ` Mark Mitchell
2005-03-26 17:48 ` Christopher Faylor
2005-03-26 19:06 ` Mark Mitchell
2005-03-26 21:03 ` Christopher Faylor
2005-03-26 22:00 ` Eli Zaretskii
2005-03-27 12:59 ` Kai Henningsen
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=20050326020850.GA19864@trixie.casa.cgf.cx \
--to=me@cgf.cx \
--cc=gdb-patches@sources.redhat.com \
--cc=mark@codesourcery.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