serious problem with cygwin and winsock?

Christopher Faylor
Wed Aug 22 09:52:00 GMT 2001

On Wed, Aug 22, 2001 at 05:58:16PM +0200, Corinna Vinschen wrote:
>On Wed, Aug 22, 2001 at 09:08:25AM +0200, Corinna Vinschen wrote:
>> I looked into and there are only a hand full of functions concerned:
>> cygwin_inet_ntoa
>> cygwin_getprotobyname
>> cygwin_getprotobynumber
>> cygwin_getservbyname
>> cygwin_getservbyport
>> cygwin_gethostbyname
>> cygwin_gethostbyaddr
>> I will add static buffers or appropriate allocation functions in the
>> next days. Fortunately these functions are defined so that the
>> allocated structure is recycled on the next call by the same process...
>I checked in a fix half an hour ago. All seven functions are now
>using a local buffer which gets allocated on demand.

Hmm.  This is basically what I was thinking of but it doesn't look like
this is a thread-safe implementation.


More information about the Cygwin-developers mailing list