Catching Memory Corruption with LLVM AddressSanitizer
Learn how LLVM's AddressSanitizer uses shadow memory and redzones to turn silent memory corruption into immediate, actionable crash reports in C/C++.
Loading…
ReadMeFeed / Community knowledge
#memory-safety
Real questions. Useful conversations. Find the people who know your stack.
llvmRust Borrow Checker: Immutable and Mutable References Cannot Alias
Rust's borrow checker prevents data races without garbage collection by enforcing that mutable and immutable references cannot alias the same data simultaneously.
rustDesigning Memory‑Safe Systems with Rust’s Ownership and Borrowing Model
An architecture note on Rust's ownership and borrowing system: requirements, minimal design, trust boundaries, operational checks, failure modes, and when to reconsider the design. Includes a concrete buffer example and verification checklist.
Rust's Ownership Model: Memory Safety Without Garbage Collection
Rust enforces memory safety at compile time through ownership, borrowing, and lifetimes—eliminating the need for a garbage collector while preventing data races and dangling pointers.
Rust ownership, borrowing, and lifetimes: preventing data races at compile time
Rust guarantees memory safety by enforcing single ownership and borrowing rules; lifetimes tie references to data, eliminating use-after-free and data races without a garbage collector.
Enabling ARM64 Memory Tagging Extension to Catch Memory Safety Bugs in C/C++
Step‑by‑step guide to enable ARM64 Memory Tagging Extension, compile a test program with -fsanitize=memtag, and verify that memory safety faults are reported via synchronous tag‑check exceptions.
Stopping Buffer Overflows with C++20 std::span
Stop passing pointer-size pairs in C++. Learn how C++20's std::span provides a safer, non-owning view of contiguous memory to prevent buffer overflows.
Ownership as a Design Constraint: Using Rust Borrowing for Compile-Time Memory Safety
Ownership in Rust is an engineering decision about who owns data, who may read it, and how long references stay valid. Using borrowing rules to shape APIs removes use-after-free and dangling pointers at compile time.
Carbon's Pointer and Reference Model: An Architecture Note on C++ Interoperability Boundaries
Carbon's experimental pointer and reference model aims to make C++ interoperability memory-safe without wrapper overhead. This architecture note examines the trust boundary, operational checks, and failure modes.