Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-class: urn:content-classes:message Subject: Re: cygwin bughunt (FAQ alert?) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 26 Jan 2005 14:29:29 +0100 Message-ID: <79F81D5F4790D344B05F489CE2AC8AB71097D8@dubexdc03.dubex.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "David Dindorp" To: X-Rescan: True X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j0QDTf2m013368 Igor Pechtchanski wrote: >> Umm, that was my bad. The thing is, "--enable-debugging" really produces >> a developer debug version, with extra tracing, etc. If all you want is a >> version of DLL with all the symbols (i.e., unstripped), the regular build >> produces that as well. Cristopher Faylor wrote: > ...and now you get to repeat these facts endlessly as people find your > words in the archives and assume that they need use this option regardless > of follow-on discussion or the FAQ. How about adding a line in the FAQ to the "how to build cygwin" (104) entry stating that the "configure ; make" mentioned does produce a Cygwin with all debugging symbols? And the link in the FAQ is wrong: "How can I debug cygwin" (entry 105) says: "To build a debugging version of the Cygwin DLL, you will need to follow the instructions at http://cygwin.com/faq/faq_3.html#SEC102." The above should point to entry 104, not 102. -- 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/