This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gethostbyname thread-safe?

On Mon, Feb 10, 2003 at 09:36:53PM -0500, Igor Pechtchanski wrote:
>On Mon, 10 Feb 2003, Ajay Nerurkar wrote:
>> Is Cygwin's gethostbyname thread-safe? From a web search I got the
>> impression that it wasn't and also that Cygwin does not have its
>> reentrant version gethostbyname_r. So, what does one do?
>> Ajay
>Looking at the code (src/winsup/cygwin/,
>964:#ifdef _MT_SAFE
>965:#define hostent_buf  _reent_winsup ()->_hostent_buf
>967:static struct hostent *hostent_buf = NULL;
>970:/* exported as gethostbyname: standards? */
>971:extern "C" struct hostent *
>972:cygwin_gethostbyname (const char *name)
>you can see that there is a provision for reentrancy.  However,
>src/winsup/cygwin/acconfig.h #undef's _MT_SAFE.  OpenGroup's specification
>says that "The gethostbyname() function need not be reentrant."
>See <> for a good
>discussion of gethostbyname() thread-safety issues.

_MT_SAFE is always set to 1 in config.h unless the dll is built with
--disable-threadsafe.  I don't know that this option even works, though.

So gethostbyname should be threadsafe.


Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]