if we are adding `brk`, let's add a small test for it? untested code might mean the first time it's silently used by a new codebase it breaks in hard to find ways. or, add a warning on it in `ASSERTIONS` mode (as e.g. we do for some syscalls). 