Tue Feb 25 14:32:00 GMT 2003
On Tue, Feb 25, 2003 at 03:18:55PM +0100, Corinna Vinschen wrote:
> On Tue, Feb 25, 2003 at 02:53:41PM +0100, Thomas Pfaff wrote:
> > SO_ERROR seems to be difficult because setsockopt does not allow to set
> > it (and i don't know which error should be set after an interrupted
> > connect. Maybe you could check this on Linux).
> I don't think SO_ERROR hurts badly. We could memorize the error code
> WSAEINTR (which should be the correct error code on an interrupted
> call) up to the next application call to Cygwin's getsockopt(SO_ERROR).
> In Cygwin's getsockopt() we can call the WinSock getsockopt and if that
> returns an error value of 0, we return the old error code instead and
WSAEINTR, that is.
> set it to 0. Otherwise we just return the new error code. From then on,
> back to normal.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:email@example.com
Red Hat, Inc.
More information about the Cygwin-developers