[Valgrind-users] Debug memory leaks

[seif e. f. <f-s...@ho...>]

valgrind --tool=memcheck --leak-check=yes --show-reachable=yes --num-callers=20 --track-fds=yes ./test
==742== Memcheck, a memory error detector
==742== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==742== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==742== Command: ./test
==742== 
==742== 
==742== FILE DESCRIPTORS: 3 open at exit.
==742== Open file descriptor 2: /dev/pts/0
==742==    <inherited from parent>
==742== 
==742== Open file descriptor 1: /dev/pts/0
==742==    <inherited from parent>
==742== 
==742== Open file descriptor 0: /dev/pts/0
==742==    <inherited from parent>
==742== 
==742== 
==742== HEAP SUMMARY:
==742==     in use at exit: 35 bytes in 2 blocks
==742==   total heap usage: 3 allocs, 1 frees, 47 bytes allocated
==742== 
==742== 35 bytes in 2 blocks are definitely lost in loss record 1 of 1
==742==    at 0x482C428: malloc (in /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
==742== 
==742== LEAK SUMMARY:
==742==    definitely lost: 35 bytes in 2 blocks
==742==    indirectly lost: 0 bytes in 0 blocks
==742==      possibly lost: 0 bytes in 0 blocks
==742==    still reachable: 0 bytes in 0 blocks
==742==         suppressed: 0 bytes in 0 blocks
==742== 
==742== For counts of detected and suppressed errors, rerun with: -v
==742== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)