> > /usr/src/lib/libc/stdlib/malloc.c says NULL, which is suprising, given > > that OpenBSD will alert me to memory issues for programs that > > run fine on another BSD. > > All the options default to off, with the partial exception of the a/A > option: the default behavior is not quite the same as either 'a' or > 'A'. > > (By default, it'll complain and abort if the internal structures get > corrupted, you make a recursive call, or you pass it particularly > bogus pointers. 'a' disables all those, while 'A' makes it also > complain and die if allocation would fail. It's probably those > default checks that are triggering the alerts you referred to.)
MALLOC_OPTIONS has a bunch of additional things, above what malloc does. But obviously even when those are not used, malloc is imposing a bunch of other paranoid features.
