Date: Sun, 13 May 2007 16:09:13 +0700 From: Max Khon <fjoe@samodelkin.net> To: Ivan Voras <ivoras@fer.hr> Cc: freebsd-arch@freebsd.org Subject: Re: HEADS DOWN Message-ID: <20070513090913.GA70647@samodelkin.net> 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
Hi! On Sun, May 13, 2007 at 02:30:29AM +0200, Ivan Voras wrote: > >> 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. That's not a valid argument. PHP developers hate apache2 and threads. So what? /fjoe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070513090913.GA70647>