Freeing xalloc'ed array

Paolo Carlini pcarlini@suse.de
Wed Oct 13 09:33:00 GMT 2004


Akim Demaille wrote:

>I'm trying to have 0 memory leak, because that's the easiest means to
>be sure you introduce no new leak.
>
Forgot to add: professional programmer arounds, using  gcc + valgrind often
prepare custom suppression files, in order to avoid spurious entries in the
valgrind reports (I'm sure they do that at CERN, f.i.)

Paolo.



More information about the Libstdc++ mailing list