Explore >> Select a destination
|
You are here 
|
thephd.dev | ||
| | | | |
blog.regehr.org
|
|
| | | | | [AI summary] The provided text is a discussion thread about undefined behavior in C and C++ programming languages, focusing on integer overflow, pointer aliasing, and compiler optimizations. Key points include the implications of undefined behavior in real-world code, the role of compilers in handling such cases, and the balance between adhering to standards and accommodating practical programming needs. The conversation touches on tools for detecting undefined behavior, the evolution of C/C++ standards, and the importance of unit testing and maintenance in software development. | |
| | | | |
www.yodaiken.com
|
|
| | | | | ||
| | | | |
erikmcclure.com
|
|
| | | | | What exactly happens when you write Foo* foo = new Foo();? A lot is packed into this one statement, so lets try to break it down. First, this example is allocating new memory on the heap, but in order to understand everything that's going on, we're going to have to explain what it means to declare a variable on the stack. If you already have a good understanding of how the stack works, and how functions do cleanup before returning, feel free to skip to the new statement. | |
| | | | |
educatedguesswork.org
|
|
| | | [AI summary] The text provides an in-depth exploration of memory management in C, covering topics such as pointer manipulation, memory allocation (malloc, free), use-after-free (UAF) bugs, and the challenges of manual memory management. It also touches on C++ as a language that offers better memory management features. The article explains how memory is allocated and deallocated, the role of the operating system in managing memory, and the potential issues like fragmentation and UAF vulnerabilities. It emphasizes the complexity of managing memory manually and hints at the benefits of higher-level languages. | ||
