Re: Compile Time Memory Leak Analyses

[Kevin Atkinson <kevina at users dot sourceforge dot net>]

On Mon, 16 Jul 2001, Tim Hollebeek wrote:

> On Mon, Jul 16, 2001 at 08:58:03AM -0400, Kevin Atkinson wrote:
> > I was wondering if anyone has given the following idea any thought:
> >
> > Provide a method of tagging functions (perhaps automatically) on the
> > memory behavior of there parameters and what they return.  That is tagging
> > each parameter which is a pointer as either unconditionally freeing a
> > pointer passed in, conditionally freeing a pointer, or never freeing a
> > pointer.  And tagging the pointer returned as always needing to be freed,
> > sometimes needing to be freed, or never needing to be freed.
>
> LCLint does something like this.

Yes but is only good for C not C++.  It would be really nice if the type
of extensive analyses the LCLint program does could be part of the Gcc
compiler, as it will work with all the languages Gcc supports.

---
Kevin Atkinson
kevina at users sourceforge net
http://www.ibiblio.org/kevina/