memory-sanitizer-benchmark
sanitizers
| memory-sanitizer-benchmark | sanitizers | |
|---|---|---|
| 2 | 49 | |
| 12 | 10,862 | |
| - | 1.7% | |
| 0.0 | 6.3 | |
| about 2 years ago | 24 days ago | |
| Shell | C | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
sanitizers
-
Good resources for learning C in depth?
AddressSanitizer is really useful, it's similar to Valgrind but has much lower overhead.
-
Memory Allocators
And if you're up for it, I'd further recommend adding some ways to deal with buffer overflows in debug builds. The way I deal with this is by using Address-Sanitizer's manual poisoning api. Bonus point if you leave additional poisoned space between allocations so off by one errors are likely to end up in a poisoned region instead of nearby allocation.
- Exception thrown: write access violation
-
2023 Stack Overflow Survey: Rust is the most admired programming language, making it the most loved language for 8 years in a row
It also doesn't hurt that Miri can find many kinds of unsafe violations even in unsafe blocks. Zig may get something like this one day, but even if it does, checking things at runtime is not a substitute for compile time -- the C++ Sanitizers haven't exactly solved the safety story for C++ even over a decade later.
-
What's the best thing you've found in code? :
This is where stuff like ASan is really useful.
-
how do I check my library for memory leaks?
Use: https://github.com/google/sanitizers/wiki/AddressSanitizer
-
Is malloc_trim() safe to use?
Have you tried using tools like ASAN/LSAN or valgrind to confirm that there are indeed no memory leaks?
-
Having trouble with projects too long to post here.
Compile with ASAN and UBSAn
- Strange Segmentation Fault when accessing a Class inside a for loop.
- Will Carbon Replace C++?
What are some alternatives?
valgrind-macos - A valgrind mirror with latest macOS support
miri - An interpreter for Rust's mid-level intermediate representation
spdlog - Fast C++ logging library.
xeus-cling - Jupyter kernel for the C++ programming language
plotters - A rust drawing library for high quality data plotting for both WASM and native, statically and realtimely 🦀 📈🚀
Catch - A modern, C++-native, test framework for unit-tests, TDD and BDD - using C++14, C++17 and later (C++11 support is in v2.x branch, and C++03 on the Catch1.x branch)
doctest - The fastest feature-rich C++11/14/17/20/23 single-header testing framework
gui_starter_template - A template CMake project to get you started with C++ and tooling
util-linux
parallax - A persistent key-value store that is embeddable and optimized for fast storage.
honggfuzz - Security oriented software fuzzer. Supports evolutionary, feedback-driven fuzzing based on code coverage (SW and HW based)
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.