mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 18:13:01 +00:00
53 lines
1.9 KiB
Plaintext
53 lines
1.9 KiB
Plaintext
|
|
searching for pointers to 11 not-freed blocks.
|
|
checked ... bytes.
|
|
|
|
80 (16 direct, 64 indirect) bytes in 1 blocks are definitely lost in loss record 11 of 11
|
|
at 0x........: malloc (vg_replace_malloc.c:...)
|
|
by 0x........: mk (leak-tree.c:11)
|
|
by 0x........: main (leak-tree.c:25)
|
|
|
|
LEAK SUMMARY:
|
|
definitely lost: 16 bytes in 1 blocks.
|
|
indirectly lost: 64 bytes in 4 blocks.
|
|
possibly lost: 0 bytes in 0 blocks.
|
|
still reachable: 96 bytes in 6 blocks.
|
|
suppressed: 0 bytes in 0 blocks.
|
|
Reachable blocks (those to which a pointer was found) are not shown.
|
|
To see them, rerun with: --show-reachable=yes
|
|
searching for pointers to 14 not-freed blocks.
|
|
checked ... bytes.
|
|
|
|
|
|
16 bytes in 1 blocks are definitely lost in loss record 1 of 14
|
|
at 0x........: malloc (vg_replace_malloc.c:...)
|
|
by 0x........: mk (leak-tree.c:11)
|
|
by 0x........: main (leak-tree.c:39)
|
|
|
|
|
|
16 bytes in 1 blocks are definitely lost in loss record 2 of 14
|
|
at 0x........: malloc (vg_replace_malloc.c:...)
|
|
by 0x........: mk (leak-tree.c:11)
|
|
by 0x........: main (leak-tree.c:38)
|
|
|
|
|
|
80 (16 direct, 64 indirect) bytes in 1 blocks are definitely lost in loss record 14 of 14
|
|
at 0x........: malloc (vg_replace_malloc.c:...)
|
|
by 0x........: mk (leak-tree.c:11)
|
|
by 0x........: main (leak-tree.c:25)
|
|
|
|
LEAK SUMMARY:
|
|
definitely lost: 48 bytes in 3 blocks.
|
|
indirectly lost: 64 bytes in 4 blocks.
|
|
possibly lost: 0 bytes in 0 blocks.
|
|
still reachable: 112 bytes in 7 blocks.
|
|
suppressed: 0 bytes in 0 blocks.
|
|
Reachable blocks (those to which a pointer was found) are not shown.
|
|
To see them, rerun with: --show-reachable=yes
|
|
|
|
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
|
|
malloc/free: in use at exit: 224 bytes in 14 blocks.
|
|
malloc/free: 14 allocs, 0 frees, 224 bytes allocated.
|
|
For a detailed leak analysis, rerun with: --leak-check=yes
|
|
For counts of detected errors, rerun with: -v
|