This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Compile Time Memory Leak Analyses
- To: Kevin Atkinson <kevina at users dot sourceforge dot net>
- Subject: Re: Compile Time Memory Leak Analyses
- From: Tim Hollebeek <tim at hollebeek dot com>
- Date: Mon, 16 Jul 2001 09:22:04 -0400
- Cc: gcc at gcc dot gnu dot org
- References: <Pine.LNX.4.33L2.0107160833320.1088-100000@kevins-linux.atkinson.inet>
- Reply-To: tim at hollebeek dot com
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.
-Tim