From owner-freebsd-arch@FreeBSD.ORG Sun May 13 22:19:01 2007 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1187A16A40F for ; Sun, 13 May 2007 22:19:01 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 0394D13C487 for ; Sun, 13 May 2007 22:19:00 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 898981A3C1A; Sun, 13 May 2007 14:54:42 -0700 (PDT) Date: Sun, 13 May 2007 14:54:42 -0700 From: Alfred Perlstein To: Ivan Voras Message-ID: <20070513215442.GZ21795@elvis.mu.org> References: <20070512153532.GQ21795@elvis.mu.org> <63984.1178992555@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-arch@freebsd.org Subject: Re: HEADS DOWN X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 May 2007 22:19:01 -0000 * Ivan Voras [070512 18:06] 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. Let's clear the issue here... FreeBSD did not have a choice in the matter. FreeBSD normally just emits a warning to stderr and does not crash your program UNLESS your errant freeing screws things up so badly that it can't help but crash... to strike a balance between diagnostics and speed certain things have to be trusted to the consumer application to avoid crashes. Normally you'd see a diagnostic along the lines of "freeing junk pointer" or something. However it can't fix all really stupid bugs and sometimes will crash. We can't be "bug for bug tolerant" with Linnex without copying their allocator. And since our allocator is vastly superior we'd be hurting all the applications that are coded correctly by doing so, along with polluting our code base with badly licensed software. -- - Alfred Perlstein