I counted a total of 58 tests for which make check-valgrind reports memory leaks. There are probably only 4 or 5 root causes.
I suggest that we divide up the work. Ben can you look at tests 169 171 and 174 -- these seem to all relate to the DATASET COPY command. And perhaps also at 383 (crosstabs). I'll look at 274 and 447. After that it seems to be test runners. It's hard to tell whether the leak is in the runner itself or within what it is testing. J' -- PGP Public key ID: 1024D/2DE827B3 fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://keys.gnupg.net or any PGP keyserver for public key.
signature.asc
Description: Digital signature
_______________________________________________ pspp-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/pspp-dev
