Lines Matching full:leaked
635 the pointer to a leaked block was lost; you have to work that out for
658 in the Valgrind gdbserver to list the addresses of the leaked blocks and/or give
1809 detailed information for each leak: the stack trace where the leaked blocks
1810 were allocated, the number of blocks leaked and their total size. When a
1829 possibly leaked blocks, .i.e those for which only an interior
1846 allocation stacks with an increased number of leaked bytes or
1861 the leaked bytes. The second command is the same as the first
2025 in command <varname>block_list</varname>) is shown before the tree was leaked.
2137 entries for which there was an increase in leaked bytes or leaked
2145 entries for which there was an increase or decrease in leaked
2146 bytes or leaked number of blocks since the previous leak search. It
2160 leak check to be leaked (i.e. the sum of direct leaks and indirect leaks),
