On Tue, 2007-01-23 at 15:49 +0100, Jim Meyering wrote: > Jim Meyering <[EMAIL PROTECTED]> wrote: > > FYI, I'll be sending a new patch soon. > > The main change will be to add new configure options: --enable-valgrind > > and --disable-valgrind. For now, the latter is the default, to minimize > > disruption, while the list of suppressions grows to accommodate the > > different operating environments used by developers who care enough to > > flip the switch. > > Here's an updated patch: > > Instrument all tests so that they are run via valgrind: > check for both errors and leaks.
This is *excellent*, thanks Jim. As soon as we have a clean run we should make ---enable-valgrind the default. It's still easy to do a valgrind-free run without re-configuring via: VALGRIND= make ... I'd much rather have people forget to turn valgrind off and trip over their memory errors than forget to turn it on and commit them to plague everyone else :) I'll start fixing errors as soon as I get the 0-9 branch merged - probably next week. Anyone who feels like fixing a memory error, please help yourself :) Cheers, Alan.
