> Which... makes sbrk() implementation a bit tricky.
I was suggesting that sbrk simply returned a single, perhaps preallocated,
block in the first call and fail in subsequent calls.
Well, if the memory is highly segmented... I guess it was some STM MCU with like... 5 or 8 separated chunks of RAM available with no contiguous addressing. I can't see how single block would work on this specific case.