02 / THE ANALYZER
Less noise.
More understanding.
No log loaded
Open a log or load the example.
YOUR WORKSPACE IS READY
The next fix starts with a log.
Open a Memcheck text log above, or choose Load example to see three real memory issues.
Select or drop a second .log / .txt file on the compare button. Current report = before.
Compare runs
Invalid reads + writes counts printed detail records, not runtime occurrences. Groups show presence in these logs; incomplete logs can omit issues. “Still leaking” includes all matching error kinds.
Grouped issues——
Valgrind errors—From ERROR SUMMARY
Definitely lost—From LEAK SUMMARY
Still reachable—Not necessarily a leak
MEMORY AT EXIT—
The details
Grouped by type & primary stackLog records are printed entries, not runtime occurrence counts. Valgrind may suppress repeats; its summary provides the total.
Original evidence
Read locally. Investigate precisely.View the example C source