The gods are not smiling on me today. Valgrind from svn from 3/22 (same as today) crashes on the simplest chromium unit test when I give the --track-origins=yes option: Plus I'm not sure I know how to retrieve old versions of the source from svn; I can do svn up -rXXXX but I suspect that doesn't get the matching VEX.
See https://bugs.kde.org/show_bug.cgi?id=188161 Reproducible on two different machines. I can still do work using an old build of valgrind from svn, but I simply can't build a good version from source anymore and have --track-origins=yes work. Maybe this is all a bad dream, and if I go back to sleep it'll go away when I wake up. - Dan ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
