Date: Tue, 19 Mar 1996 06:39:57 +0000 From: Poul-Henning Kamp <phk@critter.tfs.com> To: Narvi <narvi@haldjas.folklore.ee> Cc: Nate Williams <nate@sri.MT.net>, hackers@FreeBSD.ORG Subject: Re: CFV: adding phk_malloc to -stable Message-ID: <1695.827217597@critter.tfs.com> In-Reply-To: Your message of "Mon, 18 Mar 1996 23:48:01 %2B0200." <Pine.BSF.3.91.960318233232.5604B-100000@haldjas.folklore.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
> So why not put there a separate brach, which would contain everything > else standard but just the malloc replaced together with a warning sign? > Or just put it among the other files and make it a command line switch > for the Makefile? That everybody could get what they want - either real > stability with bad memory allocation or stability with "not so stable > malloc" + good memory allocation. (What happens if I allocate 1,000,000 > structs containing a long and a pointer?) Hrm, Hrm, I'd like to point out that phkmalloc is perfectly fine, and that no problems have been filed against it for the last N months. The problem is that >other programs< foul up their nest when using malloc. phkmalloc detects this and complains... Yes, we >may< indeed consider shipping an replacement libc. -- 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?1695.827217597>