> Thanks for the bug report, you're right -- I accidentally introduced > an error in the vector test program for gsl-1.6 (the library itself is > not affected). See patch below if you are interested.
Thanks. I am. gsl's test suite is really outstanding, and has proved invaluable in making Valgrind work reliably -- a side effect I'm sure you didn't plan on. Gold stars to all concerned. > > Is this a known problem? Has anyone [apart from me] run the gsl-1.6 > > test suite though a memory debugging tool like Valgrind or Purify? > > I usually test the releases with the bounds-checking version of gcc, > but it missed this one. I will have to start checking with valgrind > as well ;-) You should. Valgrind also tells you about computations which depend on undefined values, which is something bounds-checking gcc can't do, as far as I know. Besides, Valgrind saves you the hassle of recompiling the whole thing. J _______________________________________________ Bug-gsl mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gsl
