3 ms·
Correct, but "undefined behaviour" sometimes mean "defined by machine" I mean, pretty much the same way as int or size_t has a machine type size dependency
by raverbashing 11y ago
Correct, but "undefined behaviour" sometimes mean "defined by machine"
I mean, pretty much the same way as int or size_t has a machine type size dependency
- lmm 11y agoNot true in theory or in practice. "Undefined behaviour" has a specific meaning in terms of the C standard, distinct from "implementation-defined behaviour" like the size of int or size_t. And in practice, writing beyond the bounds of an array almost always leads to arbitrary code execution (remote in the case of a networked program), double free almost always leads to arbitrary code execution, signed integer overflow on newer compilers sometimes leads to arbitrary code execution, ...