1.5.9-1: socket() appears NOT to be thread-safe

Wed Apr 14 13:22:00 GMT 2004

On Apr 14 18:42, Enzo Michelangeli wrote:
> While porting to Cygwin the Linux application "sipd"
> (http://www.sxdesign.com/index.php?page=developer&submnu=sipd ), which
> uses pthreads, I noticed that socket() calls issued concurrently by
> several threads often failed, with strerror(errno) saying "operation not
> permitted". Once I protected all the calls with mutex locks, such errors
> went away. Is Cygwin's implementation of socket() known to be
> thread-unsafe?

No. If you can prepare a brief testcase to demonstrate the problem,
I'm happy to fix it. Of course, patches would be most welcome. See
below.
> P.S. I have written an implementation of the missing gethostbyname_r(),
> based on a mutex-protected call to gethostbyname(). If useful, I may
> gladly contribute the code.

Sure! Unfortunately, that requires us to ask you for a copyright
assignment first. See http://cygwin.com/contrib.html for details.
Corinna
-- 
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/