mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 18:13:01 +00:00
Changed some printf specifiers accordingly, plus some more that were incorrect. Also put commas in various output numbers, eg. the leak check stats. This makes them much easier to read when they get big. One exception is in XML number-only fields such as <leakedbytes>. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4874
31 lines
1.1 KiB
Plaintext
31 lines
1.1 KiB
Plaintext
|
|
searching for pointers to 1 not-freed blocks.
|
|
checked ... bytes.
|
|
|
|
LEAK SUMMARY:
|
|
definitely lost: 0 bytes in 0 blocks.
|
|
possibly lost: 0 bytes in 0 blocks.
|
|
still reachable: 2,097,152 bytes in 1 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: 2,097,152 bytes in 1 blocks.
|
|
malloc/free: 1 allocs, 0 frees, 2,097,152 bytes allocated.
|
|
For counts of detected errors, rerun with: -v
|
|
searching for pointers to 1 not-freed blocks.
|
|
checked ... bytes.
|
|
|
|
2,097,152 bytes in 1 blocks are definitely lost in loss record 1 of 1
|
|
at 0x........: malloc (vg_replace_malloc.c:...)
|
|
by 0x........: main (pointer-trace.c:24)
|
|
|
|
LEAK SUMMARY:
|
|
definitely lost: 2,097,152 bytes in 1 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
|