Also the valgrind suppressions are no longer current. See https://trac.sagemath.org/ticket/33074
On Thursday, February 24, 2022 at 1:13:47 PM UTC-8 Michael Orlitzky wrote: > On Wed, 2022-02-23 at 14:21 -0800, John H Palmieri wrote: > > > > - sage-cachegrind, sage-callgrind, sage-massif, sage-omega, > > sage-valgrind — do people use these? > > Not really, but they do have /some/ value. At the useful end, the sage- > valgrind script, > > 1. Tries to guess where the python3 suppressions file lives on your > system > 2. Adds that and some sage-specific suppressions to the command-line > 3. Sets some other default valgrind flags, and > 4. Launches valgrind on "sage-python -i" > > At the other end, sage-callgrind merely picks a log file and launches > "valgrind --tool=callgrind" on sage-ipython. > > Ultimately I think we'd be better off documenting how to run your own > valgrind installation on sage. Even the more-useful sage-valgrind > script is basically wrapping standard usage in an opaque script. But > there's certainly more egregious cruft lying around. > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/e1be9b30-e055-485a-a2d0-011b6ce58682n%40googlegroups.com.
