valgrind reports many leaks #1
Description
FYI...
From r16. Attached is the output of running the test app through valgrind. i
haven't looked closely enough to see if these were intentional or not, but
thought i'd report them nonetheless. If they are intentional, or global/shared
objects, i would recommend adding an atexit() handler to clean them up, to
avoid problems in combination with leak-checking tools.
valgrind was run like:
valgrind --leak-check=full -v --show-reachable=yes --track-origins=yes ./dotest
Happy hacking! i really like how you've separated interface/implementation here.
Original issue reported on code.google.com by sgbeal@googlemail.com on 16 Jan 2011 at 4:25
Attachments: