Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 40807 invoked from network); 2 Sep 2010 03:30:16 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Sep 2010 03:30:16 -0000 Received: (qmail 31708 invoked by uid 500); 2 Sep 2010 03:30:15 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 31331 invoked by uid 500); 2 Sep 2010 03:30:12 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 31323 invoked by uid 99); 2 Sep 2010 03:30:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Sep 2010 03:30:11 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [72.167.82.84] (HELO p3plsmtpa01-04.prod.phx3.secureserver.net) (72.167.82.84) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 02 Sep 2010 03:30:03 +0000 Received: (qmail 3777 invoked from network); 2 Sep 2010 03:29:42 -0000 Received: from unknown (76.252.112.72) by p3plsmtpa01-04.prod.phx3.secureserver.net (72.167.82.84) with ESMTP; 02 Sep 2010 03:29:42 -0000 Message-ID: <4C7F1A24.9090905@rowe-clan.net> Date: Wed, 01 Sep 2010 22:29:40 -0500 From: "William A. Rowe Jr." User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: rational behind not checking the return value of apr_palloc and apr_pcalloc References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 9/1/2010 10:17 PM, dave b wrote: > > Why not just fix it now and not worry? ... It will help if you can provide a specific use case for graceful failure. A segfault/dereference of NULL pointer provides a very specific exception for this general case, and 'recovers' neatly from a process which has simply consumed far too much memory. There are very few alloc exceptions which are recoverable a multi-client application. But if you can illustrate a few, the community is happy to evaluate your examples, which is what Jeff has politely suggested to you.