> Hmm, odd, but it's a well known phenomenon. Here's an example showing
> solely the use of cmd.exe and iexplore.exe; Cygwin not involved at all
> except for the diff command at the end.
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\Documents and Se
Sylvain Delhomme wrote on 25 September 2008 13:57:
>> The "associated udp" socket is an internal thing managed by winsock; it's
>> standard OS behaviour and happens to native win32 programs as well.
>
> I've just ported my small app to Winsock and I did not see this.
Hmm, odd, but it's a well
> The "associated udp" socket is an internal thing managed by winsock; it's
>standard OS behaviour and happens to native win32 programs as well.
I've just ported my small app to Winsock and I did not see this.
> It's
> used for some kind of internal loopbacky rpc-ish thingy and you can ignore
>
sylvain DELHOMME wrote on 25 September 2008 09:23:
> While playing with sockets and threads, I noticed that while my tcp
> socket is correctly closed, the associated udp socket (managed by Cygwin)
> is not. This was tested with(out) Firewall && Antivirus on 2 WinXP
> computers with cygwin 1.5.25.
While playing with sockets and threads, I noticed that while my tcp socket is
correctly closed, the associated udp socket (managed by Cygwin) is not. This
was tested with(out) Firewall && Antivirus on 2 WinXP computers with cygwin
1.5.25.
Is that a known problem with Cygwin (code is fine under
5 matches
Mail list logo
