Find link

language:

Find link is a tool written by Edward Betts.

searching for Memory safety 22 found (66 total)

Segmentation fault (2,433 words) [view diff] exact match in snippet view article find links to article

segmentation faults and improve memory safety. For example, Rust employs an ownership-based model to ensure memory safety. Other languages, such as Lisp

Tokio (software) (1,087 words) [view diff] no match in snippet view article

fast and resilient network servers and clients by leveraging Rust's memory-safety and concurrency features. Birmingham: Packt Publishing. ISBN 978-1-78862-171-7

Undefined behavior (2,580 words) [view diff] exact match in snippet view article find links to article

behavior in C can be broadly classified as: spatial memory safety violations, temporal memory safety violations, integer overflow, strict aliasing violations

Systems programming (716 words) [view diff] exact match in snippet view article find links to article

language often used in systems programming. Rust was designed with memory safety in mind and to be as performant as C and C++. For historical reasons

Infer Static Analyzer (780 words) [view diff] case mismatch in snippet view article find links to article

Distefano, Dino (18 April 2011). "Infer: An Automatic Program Verifier for Memory Safety of C Programs". NASA Formal Methods. Lecture Notes in Computer Science

Crash (computing) (1,430 words) [view diff] exact match in snippet view article

original on 11 December 2011. Retrieved 26 June 2014. "Jesse Ruderman » Memory safety bugs in C++ code". Squarefree.com. 1 November 2006. Archived from the

Ruffle (software) (1,202 words) [view diff] exact match in snippet view article

various security issues. The Rust language itself protects against common memory safety issues that plagued Flash Player, such as use after free or buffer overflows

Shape analysis (program analysis) (1,057 words) [view diff] exact match in snippet view article

properly freed. Shape analysis has been applied to a variety of problems: Memory safety: finding memory leaks, dereferences of dangling pointers, and discovering

C (programming language) (11,186 words) [view diff] exact match in snippet view article

Retrieved April 19, 2022. Internet Security Research Group. "What is memory safety and why does it matter?". Prossimo. Retrieved March 3, 2025. corob-msft

Intel MPX (1,267 words) [view diff] exact match in snippet view article find links to article

software-based solutions, Intel MPX provides no protection against temporal memory safety errors. Reading and writing from the doubly-indirected bounds tables

SIGPLAN (2,677 words) [view diff] case mismatch in snippet view article find links to article

Nicholas Nethercote, Julian Seward 2016 (for 2006): DieHard: Probabilistic Memory Safety for Unsafe Languages by Emery Berger, Benjamin Zorn 2015 (for 2005):

Software design pattern (3,185 words) [view diff] exact match in snippet view article find links to article

architectures support a range of atomic instructions that guarantee memory safety for modifying and accessing primitive values (integers). For example

Ntpd (526 words) [view diff] case mismatch in snippet view article find links to article

implementation of SNTP. Precision Time Protocol rdate timed Aas, Josh. "More Memory Safety for Let's Encrypt: Deploying ntpd-rs". Let's Encrypt. Let's Encrypt

AArch64 (3,318 words) [view diff] exact match in snippet view article find links to article

Developer. Retrieved 6 August 2019. "Arm MTE architecture: Enhancing memory safety". community.arm.com. 5 August 2019. Retrieved 27 July 2021. "Adopting

Null pointer (2,024 words) [view diff] case mismatch in snippet view article find links to article

Programming Language". Retrieved 17 July 2014. "Fearless Security: Memory Safety". Archived from the original on 8 November 2020. Retrieved 4 November

Roger Needham Award (322 words) [view diff] case mismatch in snippet view article find links to article

Understanding of Human Behaviour 2012 Dino Distefano [Wikidata] on Memory Safety Proofs for the Masses 2013 Boris Motik [Wikidata] on Theory and Practice:

Language-based security (2,108 words) [view diff] exact match in snippet view article find links to article

Touchstone compiler, that provides a PCC formal proof of type- and memory safety for programs implemented in Java. TAL is applicable to programming languages

SPARK (programming language) (1,478 words) [view diff] no match in snippet view article

version of the library has a complete auto-active proof of type-safety, memory-safety and some correctness properties, and retains constant-time algorithms

Suhosin (753 words) [view diff] no match in snippet view article find links to article

a segmentation fault error upon infinite recursion. Since this is a memory-safety issue, Suhosin will make the application gracefully exit once a maximum

Separation logic (3,650 words) [view diff] exact match in snippet view article find links to article

Analyses. These tools typically look for restricted classes of bugs (e.g., memory safety errors) or attempt to prove their absence, but fall short of proving

High-level language computer architecture (2,346 words) [view diff] exact match in snippet view article find links to article

security. Mainstream IT has largely moved to languages with type and/or memory safety for most applications.[citation needed] The software those depend on

V (programming language) (1,289 words) [view diff] no match in snippet view article

and contributors from around the world. V has policies to facilitate memory-safety, speed, and secure code. The language has various default features for