Date: Sun, 13 May 2007 02:30:29 +0200 From: Ivan Voras <ivoras@fer.hr> To: freebsd-arch@freebsd.org Subject: Re: HEADS DOWN Message-ID: <f25m78$ik$2@sea.gmane.org> In-Reply-To: <63984.1178992555@critter.freebsd.dk> References: <20070512153532.GQ21795@elvis.mu.org> <63984.1178992555@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Poul-Henning Kamp wrote: > In message <20070512153532.GQ21795@elvis.mu.org>, Alfred Perlstein writes: >> I like how phk malloc has it as an option. > > But notice that it is not an option for programs that runs as root > or setuid/setgid etc. > > Given the hostility of networks, I would support a more hardcore > attitude to memory mismanagement these days. Just a data point: many people were turned away from FreeBSD because a few PHP releases did a double-free or malloc-inside-signal-handler calls. Yes, GNU's malloc should have been stricter, but it's not funny when your apache crashes with SIGABORT. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGRlwlldnAQVacBcgRAvNFAJ0dSuDCSHm61kBvQypB0//vOhcfmACeMfcl sRoOAU8+BhMlzlWvCkV3obs= =G/ee -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f25m78$ik$2>