-
% valgrind --leak-check=full ./foo ==320250== Memcheck, a memory error detector ==320250== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==320250== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==320250== Command: ./foo ==320250== ==320250== ==320250== HEAP SUMMARY: ==320250== in use at exit: 4 bytes in 1 blocks ==320250== total heap usage: 23 allocs, 22 frees, 13,592 bytes allocated ==320250== ==320250== 4 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==320250== at 0x483677F: malloc (vg_replace_malloc.c:309) ==320250== by 0x109196: MAIN__ (foo.f95:4) ==320250== by 0x10925D: main (foo.f95:9) ==320250== ==320250== LEAK SUMMARY: ==320250== definitely lost: 4 bytes in 1 blocks ==320250== indirectly lost: 0 bytes in 0 blocks ==320250== possibly lost: 0 bytes in 0 blocks ==320250== still reachable: 0 bytes in 0 blocks ==320250== suppressed: 0 bytes in 0 blocks ==320250== ==320250== For lists of detected and suppressed errors, rerun with: -s ==320250== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) %
Edited by Maximilian Marx
Please register or sign in to comment