Memory leaks in compiler

[Nicholas Nethercote]

On Wed, 16 Jan 2008, Tom Tromey wrote:

> Kaveh> A valgrind suppression only silences the error for valgrind.  What if
> Kaveh> someone uses another memory checking tool?  Better to fix it for real
> Kaveh> IMHO.
>
> Add suppressions for all of them.  Any decent memory checker has to
> account for the reality that many programs don't bother freeing memory
> before exit.

Valgrind (Memcheck) generally only complains about unfreed blocks for which 
there is no pointer in live data, ie. truly leaked ones.  But it's not 
perfect, there are various ways it can be fooled.

Nick