What is the "use after free" problem? A function leaves the computed result on t... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		EVa5I7bHFq9mnYK on April 25, 2024 \| parent \| context \| favorite \| on: Borrow Checking, RC, GC, and the Eleven () Other M... What is the "use after free" problem? A function leaves the computed result on the stack or modifies data higher in the stack. There are no pointers, nothing to free.

habitue on April 25, 2024 [–]

If you return a pointer from a function that points to a stack local variable, it'll be invalid. Generally this is easy ish to detect though.

EVa5I7bHFq9mnYK on April 25, 2024 | [–]

In this stack only scheme there are no pointers. Function leaves its returned data at the top of the stack.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact