Date: Fri, 27 Sep 1996 18:42:36 +0200 From: Poul-Henning Kamp <phk@critter.tfs.com> To: Peter Wemm <peter@spinner.DIALix.COM> Cc: Poul-Henning Kamp <phk@freefall.freebsd.org>, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-lib@freefall.freebsd.org Subject: Re: cvs commit: src/lib/libc/stdlib atexit.c src/lib/libc/sys brk.2 Message-ID: <2037.843842556@critter.tfs.com> In-Reply-To: Your message of "Sat, 28 Sep 1996 00:21:19 %2B0800." <199609271621.AAA02472@spinner.DIALix.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199609271621.AAA02472@spinner.DIALix.COM>, Peter Wemm writes: >Poul-Henning Kamp wrote: >> phk 96/09/27 08:34:27 >> >> Modified: lib/libc/stdlib atexit.c >> lib/libc/sys brk.2 >> Log: >> Don't use malloc, pessimize to use sbrk. >> fix sbrk manpage while we're at it. > >Umm, you can't do this! If you use sbrk(), you are preventing the future >use of malloc(), as you *cannot* intermix the use of sbrk() and malloc() >in the same program! Well, in the general case you may not be able to, but I wrote malloc, remember ? I can! phkmalloc will notice and respect independent use of sbrk(2) :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2037.843842556>