search

zgqsdfx / ccl

Automatically exported from code.google.com/p/ccl
0 stars 0 forks source link

valgrind reports many leaks #1

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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:

GoogleCodeExporter commented 9 years ago 
The test program leaks, not the library. I have surely forgotten some
cleanups.

Original comment by jacobnav...@gmail.com on 8 Mar 2011 at 11:08

GoogleCodeExporter commented 9 years ago 
Fixed

Original comment by jacobnav...@gmail.com on 15 Apr 2011 at 10:50