This is the mail archive of the
libc-hacker@sourceware.cygnus.com
mailing list for the glibc project.
Re: malloc(0)
- To: smurf@work.noris.de (Matthias Urlichs)
- Subject: Re: malloc(0)
- From: Roland McGrath <roland@frob.com>
- Date: Thu, 4 Jun 1998 04:01:03 -0400
- Cc: libc-hacker@gnu.org
- Newsgroups: dist.glibc
> 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.
That was my point exactly, if you bothered to read the whole message. The
"problems" I referred to are anything that relies on the behavior one way
or the other, hence there is nothing gained by changing.