Now I've read this thread: What does malloc() do?
I already know from the high-level perspective what malloc does. However I want to know how an OS (Unix or Windows) interprets a malloc call.
I'm asking this because I was looking at my process list while I was stepping through a C program and noticed that the amount of memory a process takes up doesn't change after a malloc call. The process memory only changes when I attempt to read or write to an address which I allocated with malloc.
So from this I'm guessing the OS doesn't actually allocate virtual page entries for a process until it actually uses it (load/store ops). If this is the case then what does malloc() actually do at the low-level with the OS?