Thanks for correcting my misunderstandings, this is really interesting. There's quite a bit of subtlety in allocations compared to my (old) mental model of malloc calling brk().
I think you're right that I accidentally made up usage of "memory-mapped file" for mapped memory that doesn't correspond to any file. But it is possible to create them on Windows with MapViewOfFile; this function takes a handle returned from CreateFileMapping, which can accept a file handle of INVALID_HANDLE_VALUE [1]
I think you're right that I accidentally made up usage of "memory-mapped file" for mapped memory that doesn't correspond to any file. But it is possible to create them on Windows with MapViewOfFile; this function takes a handle returned from CreateFileMapping, which can accept a file handle of INVALID_HANDLE_VALUE [1]
[1] https://msdn.microsoft.com/en-gb/library/windows/desktop/aa3...