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:
“The secret of success in society, is a certain heartiness and sympathy. A man who is not happy in the company, cannot find any word in his memory that will fit the occasion. All his information is a little impertinent. A man who is happy there, finds in every turn of the conversation equally lucky occasions for the introduction of that which he has to say.”
—Ralph Waldo Emerson (1803–1882)
“For hours, in fall days, I watched the ducks cunningly tack and veer and hold the middle of the pond, far from the sportsman;... but what beside safety they got by sailing in the middle of Walden I do not know, unless they love its water for the same reason that I do.”
—Henry David Thoreau (1817–1862)