Date: Fri, 22 Nov 2002 19:36:35 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: marc@informatik.uni-bremen.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: malloc(0) broken? Message-ID: <20021122.193635.99607054.imp@bsdimp.com> In-Reply-To: <79620000.1037978720@leeloo.intern.geht.de> References: <79620000.1037978720@leeloo.intern.geht.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <79620000.1037978720@leeloo.intern.geht.de>
Marc Recht <marc@informatik.uni-bremen.de> writes:
: A malloc(0) returns always 0x800 on my system. This causes some third-party
: software to fail, because they expect malloc(0) to return NULL. Is this a
: bug or a feature? malloc(3) doesn't mention anything.
malloc(0) is undefined. If people expect it to return NULL, that
software is not standard conforming.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021122.193635.99607054.imp>