> Instead it allocates memory in chunks of the size of the system page. It can do that, it's not required to. > Also, sbrk() is a syscall, so it's not availab

> Instead it allocates memory in chunks of the size of the system page. It can do that, it's not required to. > Also, sbrk() is a syscall, so it's not available in OP's use case: he has not implemented it. Yes, they have, they just called it malloc() :-). Which was really my (admittedly fairly terse) point.