Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <3BE68FC5.C7CDF863@syntrex.com>
Date: Mon, 05 Nov 2001 14:10:29 +0100
From: Pavel Tsekov <ptsekov@syntrex.com>
MIME-Version: 1.0
To: Robert Collins <robert.collins@itdomain.com.au>
CC: cygwin@cygwin.com
Subject: Re: [PATCH] setup.exe: removes some memory leaks from fromcwd.cc
References: <3BE2CC48.47462EC6@syntrex.com>
		<1004743324.9086.39.camel@lifelesswks>  <3BE6642E.9AA62568@syntrex.com> <1004997932.1663.2.camel@lifelesswks>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Robert Collins wrote:
> 
> On Mon, 2001-11-05 at 21:04, Pavel Tsekov wrote:
> > Robert Collins wrote:
> > >
> >
> > [ snip ]
> >
> > > I haven't committed this leak - no changelog.
> >
> > Good, cause I've messed it - I'm an idiot :(. Attached is the right one.
> > And here is the Changelog entry.
> >
> 
> Thanks. Committed to HEAD.
> Feel free to find and send in such things. I've got a large chunk of
> work I hope to send a patch to cygwin-patches on tonight, which catches
> a lot of potential bugs - I've increased the compiler warning levels
> somewhat :}.
> 
> Unfortunately it's tied up with my streams work, so rather than
> committing with that in-progress (I haven't got one-of-each done yet)
> I'm going to send in a patch, which you can play with. The point of this
> is that a lot of the more mundane things you might notice should have
> been cleaned up in advance by this.

Sounds ok with me :) Btw what do you think of registering an
atexit() handler in setup so dynamically allocated global variables 
can be freed there ? This is the way I started doing the cleanup
routine at my snapshot at home. Any drawback with this approach ?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/