From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24902 invoked by alias); 21 Jan 2005 18:05:11 -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 24884 invoked from network); 21 Jan 2005 18:05:07 -0000 Received: from unknown (HELO mailsweeper.dubex.dk) (130.227.153.100) by sourceware.org with SMTP; 21 Jan 2005 18:05:07 -0000 Received: from owa.dubex.dk (unverified [130.227.153.6]) by mailsweeper.dubex.dk (Clearswift SMTPRS 5.0.4) with ESMTP id for ; Fri, 21 Jan 2005 19:05:55 +0100 Subject: Re: cygwin bughunt (FAQ alert?) Date: Fri, 21 Jan 2005 18:49:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <79F81D5F4790D344B05F489CE2AC8AB71095EC@dubexdc03.dubex.net> Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "David Dindorp" To: X-Rescan: True X-IsSubscribed: yes X-SW-Source: 2005-01/txt/msg01048.txt.bz2 Corinna Vinschen wrote: > IMHO you're looking from the wrong direction. People capable of > debugging the Cygwin DLL are usually also capable of building it. The only reason that the above is true is because you do not provide the means for people to debug the Cygwin DLL properly. > I'm wondering how somebody should be able to debug an application > at all, if this person stumbles over using the compiler tools. In the real world there is no strong binding between being able to compile a properly functioning Cygwin DLL, and being able to look through the source code, follow the developer's chain of thought and figuring out why things do not work given the appropriate debug information. You imply that in order to compile a working Cygwin, an intelligence quotient of X is required, while in order to debug it, a higher intelligence quotient X + Y is required. That's just not true. Entirely different sets of skills are involved. I'll admit though that being able to compile a functioning Cygwin makes debugging easier by removing a lot of the brain work required, and replacing it with simple trial-and-error. That approach is unfortunately just plain impossible when it comes to race conditions (eg.) or production systems. -- 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/