Developer reports
Memcheck leak-record summary
Group stated leak bytes and blocks while retaining separate error occurrences.
Your inputs
Start with an exampleYour result
Example resultAa — A small example of your colors.
How it works
Sum leakedbytes and leakedblocks from each supplied Leak_* error record. Keep final errorcounts separate; never multiply leak sizes by occurrence counts.
The sample states 100 and 20 leak-record bytes, totaling 120 across three blocks. Its repeated invalid-read count contributes no leak bytes.
Limits
A report inventory, not another Memcheck run. Reachable, indirect and other categories remain visible; totals are stated record bytes and are not asserted to be unique allocations or a clean-run verdict.