Various people have used valgrind (myself included) for checking out issues with plplot. It is a very useful tool.
I've added support for a --debug option to plplot-test.sh. By default this will run all the examples through valgrind and save the output in a log file, one file per example. This will make automatically testing the examples using valgrind much simpler. You can also add a command to the --debug option, e.g. plplot-test.sh --debug="valgrind --trace-fds=yes" if you want to use different command line options / a different debugging command. Currently only the C, C++, f77 and f95 scripts support this option. I'm not sure whether it is worth adding support for interpreted languages or other languages like java which do internal garbage collection. The changes would be relatively trivial if required. I've already spotted and fixed a couple of issues. The memory leaks for the gd driver (probably to do with libfreetype rather than plplot) are still outstanding. Note that this can take a long time to run, particularly for example 20 which has become quite slow due to the size of the images. We might want to think about a smaller image as an example. Finally, there is currently no way to use this option with ctest. I can't see an easy way without creating lots of extra tests which you wouldn't want to run all the time for speed, or making it an option set when you run cmake. Cheers Andrew ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
