Memory safety is a concern in software development that aims to avoid software bugs that cause security vulnerabilities dealing with random-access memory (RAM) access, such as buffer overflows and dangling pointers.
Computer languages such as C and C++ that support arbitrary pointer arithmetic, casting, and deallocation are typically not memory safe. There are several different approaches to find errors in such languages: see the Detection section below.
The Cyclone language uses a hybrid approach, including "fat pointers" (pointers that carry their metadata directly) and regions to give programmers some low-level control while still ensuring memory safety.
Most high-level programming languages avoid the problem by disallowing pointer arithmetic and casting entirely, and by enforcing tracing garbage collection as the sole memory management scheme.
A language could support even more uses of pointer arithmetic, casting, and deallocation without sacrificing memory safety by using automated theorem proving as a form of static code analysis. ESC/Java and D demonstrate two ways that programmers can declare their invariants in ways that can be understood by a theorem prover.
Read more about Memory Safety: Types of Memory Errors, Detection
Famous quotes containing the words memory and/or safety:
“Beauclerc: You’ve got a good memory for one who drinks.
Eddie: Drinkin’ don’t bother my memory. If it did, I wouldn’t drink. I couldn’t. You see, I’d forget how good it was. Then where’d I be? I’d start drinkin’ water again.”
—Jules Furthman (1888–1960)
“He had a gentleman-like frankness in his behaviour, and as a great point of honour as a minister can have, especially a minister at the head of the treasury, where numberless sturdy and insatiable beggars of condition apply, who cannot all be gratified, nor all with safety be refused.”
—Philip Dormer Stanhope, 4th Earl Chesterfield (1694–1773)