How Computers Work
memory leak
never freeing
Source board
This definition comes from the board below. Open it to see the term in context.
How Code Becomes ExecutionHow Computers WorkMore terms from this board
- ASTthe parsed syntax tree
- buffer overflowwriting past a buffer (overwrites the return address → exploit)
- bytecodeportable mid-level code for a VM
- CALL/RETpush-addr-and-jump / pop-and-jump
- compilersource → machine code ahead of time
- dereference (*)follow it
- GCgarbage collector (auto-frees the heap)
- interpreterruns source line-by-line
- JITcompile hot paths to native at runtime
- linkerjoins code + libraries
- pointera variable holding an address
- segfaulttouching memory you don't own
- stack frameone call's locals + args + return address
- stack overflowtoo-deep recursion
- use-after-free / dangling pointerusing freed memory