Post #3804036
2026-07-07 21:03 UTC
@JdeBP@mastodonapp.uk
If I remember correctly valgrind was hard work to get it to do what one wanted. And another poster just suggested (unconfirmed) that perhaps the gcc compiler stack thing might be able to do similar these days...
Replies (1)
-
@JdeBP@mastodonapp.uk 2026-07-07 21:31
@bytebro@mastodonapp.uk clang, not GCC. It does have a whole 'sanitization' system. I predict that it won't be any simpler for you than valgrind. (-: https://clang.llvm.org/docs/AddressSanitizer.html MSVC has a SAL system that can be useful for static, rather than runtime, checking of some stuff. https://learn.microsoft.com/en-gb/cpp/code-quality/understanding-sal My experience of valgrind is that it really really slows the program down, and generates tonnes of output that has to be sifted through. But there's no magic bullet that does away with that when one is debugging memory problems. #ComputerProgramming #clang #LLVM #MicrosoftVisualC