Re: possibly OT: threadsafe libc
Re: possibly OT: threadsafe libc
- Subject: Re: possibly OT: threadsafe libc
- From: Steve Checkoway <email@hidden>
- Date: Wed, 23 Nov 2005 05:05:33 -0800
On Nov 23, 2005, at 4:07 AM, Damien Bobillot wrote:
Steve Checkoway wrote :
From getaddrinfo(3) and getnameinfo(3):
BUGS
The implementation of getaddrinfo() is not thread-safe.
BUGS
The implementation of getnameinfo() is not thread-safe.
Mac OS X man pages are not a good reference : many are out-of-date.
Since Mac OS X 10.2, many BSD routines are threadsafe. It's the
case for getaddrinfo :
http://developer.apple.com/documentation/Performance/Conceptual/
FileSystem/Articles/ResolvingDomainNames.html
From that document:
If you are performing a simple name-to-IP lookup, you can also use
the BSD functions getipnodebyname and getipnodebyaddr instead of
getaddrinfo. In Mac OS X version 10.2 and later, these functions
are threadsafe, reentrant, and take advantage of the networking
subsystem’s IP address caching capabilities to improve performance.
As I parse those two sentences, "these functions" refer to
getipnodebyname and getipnodebyaddr. Nothing in there tells me that
getaddrinfo--and certainly not getnameinfo--is thread safe.
If the man pages are out of date and not to be trusted, then there
needs to be some documentation specifying which functions are thread
safe and when they became thread safe.
- Steve
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden