Talk:Memory safety

From Wikipedia, the free encyclopedia
Jump to: navigation, search

"security vulnerabilities" section[edit]

Some of the sentences in the "security vulnerabilities" section are incoherent, others are just wrong. For example, a stack overflow is nothing like a buffer overflow, despite the vague note about them being "similar". I'll clean it up when I get a moment. Just thought I'd make a record of it here for now. 86.128.230.251 (talk) 22:51, 10 October 2011 (UTC)

I've restructured and improved the page a bit. I changed "security vulnerabilities" to "memory errors" because some of them are not exploitable. --Crashie (talk) 13:37, 27 November 2011 (UTC)

Michael Hicks[edit]

He has something to say on this article's definitions: http://www.pl-enthusiast.net/2014/07/21/memory-safety/ --Nemo 21:21, 30 October 2014 (UTC)

No mention of Rust and similar solutions[edit]

The article only states that most high-level languages use tracing garbage collection to avoid memory safety problems. We should mention that some languages, like Rust, use static analysis to fix the problem without having to rely on garbage collection. Munksgaard (talk) 10:20, 31 May 2015 (UTC)