(All that said, embedded systems sometimes don't have virtual memory, so the original problem stated in the link is just not a thing...) > working from a fixed

(All that said, embedded systems sometimes don't have virtual memory, so the original problem stated in the link is just not a thing...) > working from a fixed-size pool or arena created in code (possibly itself carved out of RAM with malloc(), but importantly only once at first setup, where you have a better guarantee that the allocation will succeed) And I should add to this that you probably want to access all of the pool/arena to do setup, or just ensure it's physically allocated if you are running in a virtual memory space. This is something that is reasonable at setup time, though.