Search for the line: "The lookup functions above all have one in common: they are not reentrant and therefore unusable in multi-threaded applications. Therefore provides the GNU C library a new set of functions which can be used in this context."
Perhaps it operates differently if _POSIX_SOURCE is defined or this documentation is old although the former doesn't seem to be the case. john On Tue, Mar 27, 2012 at 10:52 AM, Alan M. Carroll < a...@network-geographics.com> wrote: > Where do you see that? My browser claims only one mention of getaddrinfo > on that page > > "You can also use getaddrinfo and getnameinfo to obtain this information" > > which contains no mention of thread safety. The glibc documentation for > getaddinfo > > http://www.gnu.org/software/gnulib/manual/html_node/getaddrinfo.html > > just refers to the POSIX specification > > http://pubs.opengroup.org/onlinepubs/9699919799/functions/getaddrinfo.html > > which states > > The freeaddrinfo() and getaddrinfo() functions shall be thread-safe. > > > Tuesday, March 27, 2012, 11:27:34 AM, you wrote: > > > FYI: According to > > > http://www.gnu.org/software/libc/manual/html_node/Host-Names.html > > > The glibc versions of getaddrinfo are still not thread safe. > >
