Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 15 Apr 2004 13:41:18 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: 1.5.9-1: socket() appears NOT to be thread-safe Message-ID: <20040415174118.GA8644@coe.bosbc.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <00c901c4220d$47f6eaa0$0200a8c0@em.noip.com> <011301c42298$19414da0$0200a8c0@em.noip.com> <20040415041455.GA998@coe.bosbc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040415041455.GA998@coe.bosbc.com> User-Agent: Mutt/1.4.1i On Thu, Apr 15, 2004 at 12:14:55AM -0400, Christopher Faylor wrote: >On Thu, Apr 15, 2004 at 11:16:03AM +0800, Enzo Michelangeli wrote: >>What I can do for the time being is to provide the testcase that Corinna >>asked for (attached below). Here are the results: > >I can duplicate the behavior noted here. > >I sent Corinna a patch in private email. I'm not thrilled with it but >it does seem to alleviate the problem. > >The problem seems to be that winsock's socket is not multi-thread safe. >That is very hard for me to believe but the strace output seems to >confirm it. Corinna showed me that this was a problem in my autoload code rather than a problem with winsock. That's comforting. I guess I've grown too quick to judge Windows. I've checked in a fix and am regenerating a snapshot. The fix consisted of deleting a few lines of code so that's always nice... Thanks for the test case. It helped a lot in tracking this problem down. cgf -- 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/