memory-sanitizer-benchmark
valgrind-macos
| memory-sanitizer-benchmark | valgrind-macos | |
|---|---|---|
| 2 | 6 | |
| 12 | 1,073 | |
| - | - | |
| 0.0 | 8.7 | |
| about 2 years ago | 9 days ago | |
| Shell | C | |
| Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
memory-sanitizer-benchmark
-
Valgrind 3.21 Released
Yes, there are some errors reported by Valgrind that are not detected by AddressSanitizer. The opposite is also true: AddressSanitizer finds problems that are not reported by Valgrind. Here are some sources with errors reported by Valgrind only (Valgrind 3.18 vs ASan from GCC 12).
-
Comparing Memory Sanitizers
Since then I have been able to test these tools more thoroughly and I reported the results in this post as well as in a public repository.
valgrind-macos
-
macOS Sonoma Forced Installs
> There's a nice synergy between using Mac and Linux - many of the same scripts, commands, and concepts work identically.
I switched to a Mac a few months ago from Windows and I kinda hate the small differences with Linux, I like WSL much better. On top of my head,
- No systemd
- No native docker
- No valgrind (there is https://github.com/LouisBrunner/valgrind-macos though)
I basically have to install a Linux VM on Mac just for this, at which point WSL on Windows is a much better tradeoff IMO.
-
I find it's not possible to do serious C/C++ coding on latest macOS
As far as I know there are only two of us contributing to it - Louis Brunner and myself, both very much part time volunteers.
-
Valgrind 3.21 Released
There is ongoing work here https://github.com/LouisBrunner/valgrind-macos (and I have a repo that is based on the same changes, and a bit more up do date upstream here https://github.com/paulfloyd/macos_valgrind). Anyone that can help with this is most welcome!
-
Apple killed XVim
BTW, it seems like there is some work ongoing for working Valgrind in later macOS versions: https://github.com/LouisBrunner/valgrind-macos/issues/19
What are some alternatives?
oni2 - Native, lightweight modal code editor
GLFW - A multi-platform library for OpenGL, OpenGL ES, Vulkan, window and input
gperftools - Main gperftools repository
htop - htop - an interactive process viewer
valgrind-riscv64 - Valgrind with support for the RISCV64/Linux platform.
verrou - floating-point errors checker
ocreval - Update of the ISRI Analytic Tools for OCR Evaluation with UTF-8 support
BlackHole - BlackHole is a modern macOS audio loopback driver that allows applications to pass audio to other applications with zero additional latency.
macos_valgrind - Official Valgrind source merged with Louis Brunner's github repo