4 ms·
use after free is really about the consequences of use-after-reuse. The bug is always there, but you don't notice the behavior until someone changes the data ou
by hinkley 4y ago
use after free is really about the consequences of use-after-reuse. The bug is always there, but you don't notice the behavior until someone changes the data out from under you. Until someone reuses the memory allocation, your app appears to be working properly.
- anthomtb 4y agoI understand your point. My comment was a weak attempt at being clever. Free (the concept) versus free(void* ptr) (the function call) - the latter would not be present without dynamic allocation.