gnupic: Re: [gnupic] gpasm memory leaks


Previous by date: 1 Jun 2007 08:17:29 +0100 Re: [gnupic] gpasm memory leaks, Tamas Rudnai
Next by date: 1 Jun 2007 08:17:29 +0100 Re: [gnupic] gpasm memory leaks, David Barnett
Previous in thread: 1 Jun 2007 08:17:29 +0100 Re: [gnupic] gpasm memory leaks, Tamas Rudnai
Next in thread: 1 Jun 2007 08:17:29 +0100 Re: [gnupic] gpasm memory leaks, David Barnett

Subject: Re: [gnupic] gpasm memory leaks
From: Robert Pearce ####@####.####
Date: 1 Jun 2007 08:17:29 +0100
Message-Id: <20070601081725.a340f22d.rob@bdt-home.demon.co.uk>

On Thu, 31 May 2007 17:32:02 -0500 David wrote:
> BTW, for those 
> experienced with fixing memory leaks in C, is the technique of passing a 
> reference/pointer down instead of returning one up a common fix? 

It's not really a fix, it just allows a little more flexibility for the caller. Actually, a lot of the standard C library functions do it the other way - for example, strdup calls malloc internally and expects the programmer to call free on the returned string. So it would probably be fair to answer "no" to your question.

As to your CVS question, my version of SVN rejects "svn diff -u". I believe the CVS equivalent of "svn diff -x -u" is "cvs diff -u".

Cheers,
Rob

Previous by date: 1 Jun 2007 08:17:29 +0100 Re: [gnupic] gpasm memory leaks, Tamas Rudnai
Next by date: 1 Jun 2007 08:17:29 +0100 Re: [gnupic] gpasm memory leaks, David Barnett
Previous in thread: 1 Jun 2007 08:17:29 +0100 Re: [gnupic] gpasm memory leaks, Tamas Rudnai
Next in thread: 1 Jun 2007 08:17:29 +0100 Re: [gnupic] gpasm memory leaks, David Barnett


Powered by ezmlm-browse 0.20.