From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7522 invoked by alias); 28 Dec 2004 22:29:52 -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 7450 invoked from network); 28 Dec 2004 22:29:40 -0000 Received: from unknown (HELO smtp10.wanadoo.fr) (193.252.22.21) by sourceware.org with SMTP; 28 Dec 2004 22:29:40 -0000 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1007.wanadoo.fr (SMTP Server) with SMTP id 942A5280013B; Tue, 28 Dec 2004 23:29:39 +0100 (CET) Received: from [192.168.2.103] (ALagny-151-1-21-16.w83-114.abo.wanadoo.fr [83.114.115.16]) by mwinf1007.wanadoo.fr (SMTP Server) with ESMTP id 74E6D280012D; Tue, 28 Dec 2004 23:29:38 +0100 (CET) Message-ID: <41D1DEA4.1080304@exalead.com> Date: Tue, 28 Dec 2004 22:29:00 -0000 From: Stephane Donze User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: "Hyperthreading" problems References: <41D1D2B2.4030200@exalead.com> In-Reply-To: <41D1D2B2.4030200@exalead.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-12/txt/msg00927.txt.bz2 Hi, Thank you for your reply. You are right, I did not look at the code, and I certainly do not pretend to be able to fix this problem. I am sorry to have to say that, but your message is a very good example of the fundamental difference between a project that is useable and reliable, and a project that "almost works" and will never do more that that. The problem I reported is known for almost 2 years (posted by Henrik Wist, 20 Mar 2003, subject was "cygwin commands sometime hang on dual-processor (WinNT-SP5)"). I don't care if it is the same bug or not, the fact is that cygwin has a critical problem (i.e. something that prevent users to use even simple commands like 'ls' !!) on multiprocessor machines and nobody seems to care about it. You cannot just expect people to "wait until you someday have a system that shows the problem" everytime they encounter a bug. If you guys want cygwin to be used by real people, in real life production or development environments, you should go a bit further than "I don't have the problem on my computer, so fix it yourself". If you don't want to or are not able to pay attention to "real world" bugs, cygwin will probably never be more than an "almost working" program that runs on your computer the time to take nice screenshots, but fails miserably when users try to make it work in the real life. Regards, Stephane NB: this post is not at all about "commercial software versus OSS", there are lots of "industrial quality" open source projects like Apache, MySQL, etc. Christopher Faylor wrote: > On Fri, Dec 24, 2004 at 09:01:17AM +0100, St?phane Donz? wrote: > >> we have encountered random hangs and crashes in cygwin (see output of >> cygcheck attached to this message) on a dual-processor server running >> Windows Server 2003. IMHO, the so-called "hyperthreading problems" >> reported >> recently on this mailing list just have nothing to do with >> hyperthreading, >> but are more generally related to multi-processor issues. > > > If you have followed the thread, then you know that I have a > multi-processor > system and I don't have the problem. > >> > > There is no point in reposting scripts. There is no point in > recapitulating the problem. There is no point in making obvious > observations about what one would suspect the cause would be without > bothering to look at the code. > > Your options are to fix the problem yourself or wait until I someday > have a system which demonstrates the problem. > > 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/