http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48700
Summary: [OOP] memory leak with MOVE_ALLOC of polymorphic variables Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassig...@gcc.gnu.org ReportedBy: sfilipp...@uniroma2.it Created attachment 24058 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24058 test-case Running the attached test case through valgrind gives memory leak warnings, both with current trunk and 4.6.0 ---------------------------------------------------------------------------- [sfilippo@donald bug31]$ gfortran -v Using built-in specs. COLLECT_GCC=gfortran COLLECT_LTO_WRAPPER=/usr/local/gnu47/libexec/gcc/x86_64-unknown-linux-gnu/4.7.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ../gcc/configure --prefix=/usr/local/gnu47 --enable-languages=c,c++,fortran --with-gmp=/home/travel/GNUBUILD/gmp --with-mpfr=/home/travel/GNUBUILD/mpfr --with-mpc=/home/travel/GNUBUILD/mpc : (reconfigured) ../gcc/configure --prefix=/usr/local/gnu47 --enable-languages=c,c++,fortran --with-gmp=/home/travel/GNUBUILD/gmp --with-mpfr=/home/travel/GNUBUILD/mpfr --with-mpc=/home/travel/GNUBUILD/mpc : (reconfigured) ../gcc/configure --prefix=/usr/local/gnu47 --enable-languages=c,c++,fortran --with-gmp=/home/travel/GNUBUILD/gmp --with-mpfr=/home/travel/GNUBUILD/mpfr --with-mpc=/home/travel/GNUBUILD/mpc Thread model: posix gcc version 4.7.0 20110418 (experimental) (GCC) [sfilippo@donald bug31]$ gfortran -o testmv3 testmv3.f90 -ggdb [sfilippo@donald bug31]$ valgrind --leak-check=full ./testmv3 ==25909== Memcheck, a memory error detector ==25909== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==25909== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info ==25909== Command: ./testmv3 ==25909== ==25909== ==25909== HEAP SUMMARY: ==25909== in use at exit: 216 bytes in 4 blocks ==25909== total heap usage: 26 allocs, 22 frees, 12,368 bytes allocated ==25909== ==25909== 40 bytes in 1 blocks are definitely lost in loss record 3 of 4 ==25909== at 0x4A05E46: malloc (vg_replace_malloc.c:195) ==25909== by 0x401425: MAIN__ (testmv3.f90:37) ==25909== by 0x401729: main (testmv3.f90:22) ==25909== ==25909== 176 (96 direct, 80 indirect) bytes in 1 blocks are definitely lost in loss record 4 of 4 ==25909== at 0x4A05E46: malloc (vg_replace_malloc.c:195) ==25909== by 0x400DCF: MAIN__ (testmv3.f90:30) ==25909== by 0x401729: main (testmv3.f90:22) ==25909== ==25909== LEAK SUMMARY: ==25909== definitely lost: 136 bytes in 2 blocks ==25909== indirectly lost: 80 bytes in 2 blocks ==25909== possibly lost: 0 bytes in 0 blocks ==25909== still reachable: 0 bytes in 0 blocks ==25909== suppressed: 0 bytes in 0 blocks ==25909== ==25909== For counts of detected and suppressed errors, rerun with: -v ==25909== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 6 from 6)