top | item 45115646 (no title) ixwt | 6 months ago This is a simple use after free on the stack. Is that UB? discuss order hn newest jibal|6 months ago Yes, of course ... the content of freed memory, on the stack or otherwise, is not defined. (And this is not in fact on the stack.) ixwt|6 months ago 1. I'm fairly certain you have to use make to get into heap.2. Odin 0s out memory when declaring a variable unless you explicitly state so with ---. This defines the state of memory when allocated. load replies (1) psychoslave|6 months ago Isn't there a cheap way to implement a gentle refusal to compile a code if it is not garantee that it won't prevent such a behavior? load replies (2)
jibal|6 months ago Yes, of course ... the content of freed memory, on the stack or otherwise, is not defined. (And this is not in fact on the stack.) ixwt|6 months ago 1. I'm fairly certain you have to use make to get into heap.2. Odin 0s out memory when declaring a variable unless you explicitly state so with ---. This defines the state of memory when allocated. load replies (1) psychoslave|6 months ago Isn't there a cheap way to implement a gentle refusal to compile a code if it is not garantee that it won't prevent such a behavior? load replies (2)
ixwt|6 months ago 1. I'm fairly certain you have to use make to get into heap.2. Odin 0s out memory when declaring a variable unless you explicitly state so with ---. This defines the state of memory when allocated. load replies (1)
psychoslave|6 months ago Isn't there a cheap way to implement a gentle refusal to compile a code if it is not garantee that it won't prevent such a behavior? load replies (2)
jibal|6 months ago
ixwt|6 months ago
2. Odin 0s out memory when declaring a variable unless you explicitly state so with ---. This defines the state of memory when allocated.
psychoslave|6 months ago