3 ms·
Anatomy of a Program in Memory (2009)
- linkdd 5y agoImages are served over HTTP while the website is served over HTTPS. Chrome blocks them.
- colejohnson66 5y agoRunning it through the Web Archive turns the whole thing into HTTP: http://web.archive.org/web/20210417040704/https://manybutfinite.com/post/anatomy-of-a-program-in-memory/ http://web.archive.org/web/20210417040704/https://manybutfin...
- 1vuio0pswjnm7 5y agoRedirects to manybutfinite.com
- colejohnson66 5y agoSpecifically, https://manybutfinite.com/post/anatomy-of-a-program-in-memory/ https://manybutfinite.com/post/anatomy-of-a-program-in-memor...
- userbinator 5y agoAll the diagrams that show the stack "above" the heap may be an example of a widespread "UNIX-ism"; and indeed, there are many questions on StackOverflow and the like from semi-confused beginners wondering why they see heap allocations having higher addresses than ones on the stack. In Windows, stacks are usually very low in memory, even below the process image itself (which is normally loaded at 4MB[1]), and heaps are above. Of course, if you have many threads, stack and heap ranges can end up anywhere, but in the simplest single-thread case the layout is already very different from the "classic" image-heap-stack order. [1]https://devblogs.microsoft.com/oldnewthing/20141003-00/?p=43923 https://devblogs.microsoft.com/oldnewthing/20141003-00/?p=43...