Date: Tue, 15 May 2007 14:09:23 +0300 From: Giorgos Keramidas <keramida@freebsd.org> To: Ivan Voras <ivoras@fer.hr> Cc: freebsd-arch@freebsd.org Subject: Re: HEADS DOWN Message-ID: <20070515110923.GA4471@kobe.laptop> In-Reply-To: <f25m78$ik$2@sea.gmane.org> References: <20070512153532.GQ21795@elvis.mu.org> <63984.1178992555@critter.freebsd.dk> <f25m78$ik$2@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2007-05-13 02:30, Ivan Voras <ivoras@fer.hr> wrote: >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. This seems to imply that not crashing would somehow be better. But I doubt anybody would be happy if they realized that their PHP randomly corrupted user data because the system malloc() implementation was not strict enough. While I agree that an Apache server crashing is a bar thing, I don't buy into the mindset that would accept random heap corruption because "not crashing would be good". - Giorgos
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070515110923.GA4471>