From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9083 invoked by alias); 15 Apr 2004 04:04:26 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 9022 invoked from network); 15 Apr 2004 04:04:24 -0000 Received: from unknown (HELO emethist.hknet.com) (202.67.240.233) by sources.redhat.com with SMTP; 15 Apr 2004 04:04:24 -0000 Received: from em.no-ip.com (vp187108.hk.uac65.hknet.com [203.169.187.108]) by emethist.hknet.com (Postfix) with ESMTP id 6E23E44481; Thu, 15 Apr 2004 12:04:22 +0800 (HKT) Received: from emnb (emnb [192.168.0.2]) by em.no-ip.com (8.11.6/8.8.7) with SMTP id i3F43Zi10429; Thu, 15 Apr 2004 12:03:35 +0800 Message-ID: <013701c4229e$9cd68c60$0200a8c0@em.noip.com> From: "Enzo Michelangeli" To: Cc: "\"Brian Ford\"" Subject: Re: 1.5.9-1: socket() appears NOT to be thread-safe Date: Thu, 15 Apr 2004 04:04:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-SW-Source: 2004-04/txt/msg00521.txt.bz2 I wrote: ----- Original Message ----- From: "Enzo Michelangeli" To: Cc: ""Brian Ford"" Sent: Thursday, April 15, 2004 11:16 AM Subject: Re: 1.5.9-1: socket() appears NOT to be thread-safe [...] > By the way, even in case of no error the socket calls return the same > value of fd. Is this OK?? Please ignore the two lines above: I forgot to remove them after fixing the bug that had prompted me to write them in first place :-) The fd are obviously different, as shown in the sample output. Enzo P.S. By the way, Corinna: couldn't I just put my gethostbyname_r() in the public domain, rather than going through the bureaucratic chore of the copyright assignment? Also because I feel that implementing it through mutex-protection of gethostbyname(), as I did, is just a quick hack, as it unnecessarily blocks other threads that could access the name server in parallel (with separate network I/O and properly re-entrant code). It may help other implementors to solve an urgent problem, but I don't think it should be released as part of the Cygwin code. -- 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/