This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: --enable-debugging
- To: Matt <matt at use dot net>
- Subject: Re: --enable-debugging
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Fri, 11 Feb 2000 16:37:12 -0500
- Cc: DJ Delorie <dj at delorie dot com>, cygwin-developers at sourceware dot cygnus dot com
- References: <200002111838.NAA12005@envy.delorie.com> <Pine.NEB.4.10.10002111258260.19633-100000@cesium.clock.org>
- Reply-To: cygwin-developers at sourceware dot cygnus dot com
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