malloc(0)

[Matthias Urlichs]

  Roland McGrath <roland@frob.com> writes:
> 
> Ours is not the only system with this behavior, so programs with such
> problems have them regardless and will be fixed if anyone cares.
> 
Some programs use autoconf or whatever to detect whether they need to check
for X!=0 before blindly calling assert((foo=malloc(X))!=0).

Since this check is then encased in the program's binary shrine, changing
libc behavior from under them isn't going to sit well with users.

-- 
Matthias Urlichs
noris network GmbH