mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 10:05:29 +00:00
7c542ccd39
seem to be simply duplication of the x86 instruction set tests into the addrcheck and helgrind trees. I'm not sure what this duplication achieves. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3264
46 lines
1.7 KiB
Plaintext
46 lines
1.7 KiB
Plaintext
|
|
searching for pointers to 18 not-freed blocks.
|
|
checked ... bytes.
|
|
|
|
24 (8 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record 15 of 18
|
|
at 0x........: malloc (vg_replace_malloc.c:...)
|
|
by 0x........: mk (leak-cycle.c:11)
|
|
by 0x........: mkcycle (leak-cycle.c:22)
|
|
by 0x........: main (leak-cycle.c:36)
|
|
|
|
|
|
24 (8 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record 16 of 18
|
|
at 0x........: malloc (vg_replace_malloc.c:...)
|
|
by 0x........: mk (leak-cycle.c:11)
|
|
by 0x........: mkcycle (leak-cycle.c:22)
|
|
by 0x........: main (leak-cycle.c:37)
|
|
|
|
|
|
48 (8 direct, 40 indirect) bytes in 1 blocks are definitely lost in loss record 17 of 18
|
|
at 0x........: malloc (vg_replace_malloc.c:...)
|
|
by 0x........: mk (leak-cycle.c:11)
|
|
by 0x........: mkcycle (leak-cycle.c:22)
|
|
by 0x........: main (leak-cycle.c:45)
|
|
|
|
|
|
48 (8 direct, 40 indirect) bytes in 1 blocks are definitely lost in loss record 18 of 18
|
|
at 0x........: malloc (vg_replace_malloc.c:...)
|
|
by 0x........: mk (leak-cycle.c:11)
|
|
by 0x........: mkcycle (leak-cycle.c:22)
|
|
by 0x........: main (leak-cycle.c:59)
|
|
|
|
LEAK SUMMARY:
|
|
definitely lost: 32 bytes in 4 blocks.
|
|
indirectly lost: 112 bytes in 14 blocks.
|
|
possibly lost: 0 bytes in 0 blocks.
|
|
still reachable: 0 bytes in 0 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: 144 bytes in 18 blocks.
|
|
malloc/free: 18 allocs, 0 frees, 144 bytes allocated.
|
|
For a detailed leak analysis, rerun with: --leak-check=yes
|
|
For counts of detected errors, rerun with: -v
|