Lines Matching full:blocks
87 blocks has been removed. The tool has accordingly been renamed to
181 269884 == 250101 (overhead for huge blocks exhausts space too soon)
453 of heap blocks (as allocated with malloc/new/new[]), it instead
480 show possibly-lost blocks.
483 has been added. DHAT keeps track of allocated heap blocks, and also
583 206600 Leak checker fails to upgrade indirect blocks when their
769 --leak-check=summary counted "indirectly lost" blocks and
770 "suppressed" blocks as "definitely lost".
772 - Blocks that are only reachable via at least one interior-pointer,
780 fewer leaked blocks.
998 added. It is similar to VALGRIND_COUNT_LEAKS but counts blocks
1358 arbitrarily far out-of-bounds accesses to heap blocks, and it can
1359 detect accesses heap blocks that have been freed a very long time
1360 ago (millions of blocks in the past).
1582 which have a million or more malloc'd blocks in use at once. These
1670 shows the addresses of superblocks (code blocks) as they are executed.
2460 - Programs that allocate many heap blocks may run faster, due to
2743 natively (not on valgrind). That is, if a syscall blocks only the
3062 natively (not on valgrind). That is, if a syscall blocks only the
