Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Fri, 11 Feb 2000 16:37:12 -0500 From: Chris Faylor To: Matt Cc: DJ Delorie , cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: --enable-debugging Message-ID: <20000211163712.A13791@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com References: <200002111838 DOT NAA12005 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.3i In-Reply-To: ; from matt@use.net on Fri, Feb 11, 2000 at 01:23:22PM -0800 On Fri, Feb 11, 2000 at 01:23:22PM -0800, Matt wrote: >On Fri, 11 Feb 2000, DJ Delorie wrote: > >> I've modified the snapshot script to add --enable-debugging in the >> configure command. This may help us track down some problems people >> have been reporting. If you have your own build, please add >> --enable-debugging to your configure as well. Hopefully we'll find >> more bugs (and their solutions ;) this way. >> >> Tonight's snapshot will be the first with this option, assuming it works. > >A suggestion-- > >Gathering lint output on the code with each automated build would help as >well. This is something we started doing at my work and it has been really >useful in tracking down bugs while relieving individual developers from >the efforts of running lint on their code and relying on them to go >through the output themselves on a regular basis. The cygwin code is already compiled with -Wall. I suppose that it is possible that lint could pick up more errors but I actually don't have a lint on my Red Hat 6.0 system and it would have to be lint++ to handle C++, wouldn't it? cgf