Skip to content

Instantly share code, notes, and snippets.

Created Jul 21, 2016
Embed
What would you like to do?
valgrind output
==9650== Memcheck, a memory error detector
==9650== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==9650== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==9650== Command: ./recover
==9650==
==9650==
==9650== HEAP SUMMARY:
==9650== in use at exit: 568 bytes in 1 blocks
==9650== total heap usage: 53 allocs, 52 frees, 30,048 bytes allocated
==9650==
==9650== 568 bytes in 1 blocks are still reachable in loss record 1 of 1
==9650== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==9650== by 0x51AB44C: __fopen_internal (iofopen.c:73)
==9650== by 0x400B4E: showmethepix (recover.c:76)
==9650== by 0x400B91: showmethepix (recover.c:82)
==9650== by 0x400B91: showmethepix (recover.c:82)
==9650== by 0x400B91: showmethepix (recover.c:82)
==9650== by 0x400B91: showmethepix (recover.c:82)
==9650== by 0x400B91: showmethepix (recover.c:82)
==9650== by 0x400B91: showmethepix (recover.c:82)
==9650== by 0x400B91: showmethepix (recover.c:82)
==9650== by 0x400B91: showmethepix (recover.c:82)
==9650== by 0x400B91: showmethepix (recover.c:82)
==9650==
==9650== LEAK SUMMARY:
==9650== definitely lost: 0 bytes in 0 blocks
==9650== indirectly lost: 0 bytes in 0 blocks
==9650== possibly lost: 0 bytes in 0 blocks
==9650== still reachable: 568 bytes in 1 blocks
==9650== suppressed: 0 bytes in 0 blocks
==9650==
==9650== For counts of detected and suppressed errors, rerun with: -v
==9650== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment