Date: Thu, 24 Jul 2003 15:52:04 -0700 From: Michael Sierchio <kudzu@tenebras.com> To: freebsd-stable@freebsd.org Subject: Re: malloc does not return null when out of memory Message-ID: <3F206314.7000602@tenebras.com> In-Reply-To: <20030724213818.46089.qmail@web14807.mail.yahoo.com> References: <20030724213818.46089.qmail@web14807.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Rostislav Krasny wrote: >>>The Single UNIX Specification extends malloc() function, a little. >>>Following URL is of the manual page of this function: >>>http://www.opengroup.org/onlinepubs/007904975/functions/malloc.html >>>Read "ERRORS" and "Issue 6" sections. Should FreeBSD be conformed > > to > >>>this standard? >> >>FreeBSD malloc is POSIX/SUSv3 compliant. It returns NULL and sets >>errno to ENOMEM if insufficient storage space is available. > > > Then why Gabor <gabor@vmunix.com> reported that it doesn't return NULL > when insufficient storage space is available? Am I misunderstand something? There was sufficient storage space -- sadly, we had to shoot your mother in order to get it. ;-) Running up against VM limits is inherently ugly. The OP is running in 64MB w/o swap. I have a Soekris box myself. Process limits are your friend.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F206314.7000602>