4 ms·
https://stackoverflow.com/a/45248015 https://stackoverflow.com/a/45248015
by carlmr 2y ago
https://stackoverflow.com/a/45248015 https://stackoverflow.com/a/45248015
- amelius 2y agoThanks, but I think I looked into that when I ran into the problem. Iirc, the main problem was that most Python modules are not designed with Valgrind in mind (so they generate a lot of noisy/irrelevant warnings and errors) I wish module maintainers would make running Valgrind a part of their QC process.
- carlmr 2y agoUnderstandable. I don't think there's a good way around this though. Even if you run valgrind on a C++ repo that hasn't seen much valgrind use, you'll get a lot of output. But that output is because the memory management is usually broken in every larger C++ repo which isn't developed by a small team of experts.