Lines Matching full:leaked
639 the pointer to a leaked block was lost; you have to work that out for
662 in the Valgrind gdbserver to list the addresses of the leaked blocks and/or give
1901 detailed information for each leak: the stack trace where the leaked blocks
1902 were allocated, the number of blocks leaked and their total size. When a
1928 possibly leaked blocks, .i.e those for which only an interior
1945 allocation stacks with an increased number of leaked bytes or
1960 the leaked bytes. The second command is the same as the first
2124 in command <varname>block_list</varname>) is shown before the tree was leaked.
2236 entries for which there was an increase in leaked bytes or leaked
2244 entries for which there was an increase or decrease in leaked
2245 bytes or leaked number of blocks since the previous leak search. It
2259 leak check to be leaked (i.e. the sum of direct leaks and indirect leaks),
