------- Comment #4 from paul dot richard dot thomas at gmail dot com
2010-02-25 12:50 -------
Subject: Re: Memory leaks in allocatable component
expressions
> ------- Comment #3 from burnus at gcc dot gnu dot org 2010-02-25 07:38
> -------
> Paul, can you try with valgrind --leak-check=full ? Without the =full option,
> I also do not get any line info output but just in the summary "definitely
> lost: 288 bytes in 4 blocks".
Tobias,
I cannot remember how valgrind puts it but I get the no memory leaks
possible message, even with =full.
Cheers
Possible
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38319
