Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54486 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75584 invoked from network); 9 Aug 2011 07:19:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Aug 2011 07:19:59 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.210.172 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.210.172 mail-iy0-f172.google.com Received: from [209.85.210.172] ([209.85.210.172:43290] helo=mail-iy0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C7/00-09638-E9FD04E4 for ; Tue, 09 Aug 2011 03:19:58 -0400 Received: by iye7 with SMTP id 7so12702881iye.31 for ; Tue, 09 Aug 2011 00:19:55 -0700 (PDT) Received: by 10.42.149.133 with SMTP id w5mr6888754icv.102.1312874395518; Tue, 09 Aug 2011 00:19:55 -0700 (PDT) Received: from [192.168.200.5] (c-50-131-46-20.hsd1.ca.comcast.net [50.131.46.20]) by mx.google.com with ESMTPS id v16sm4819084ibf.42.2011.08.09.00.19.54 (version=SSLv3 cipher=OTHER); Tue, 09 Aug 2011 00:19:54 -0700 (PDT) Message-ID: <4E40DF99.70601@lerdorf.com> Date: Tue, 09 Aug 2011 00:19:53 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110627 Thunderbird/5.0 MIME-Version: 1.0 To: Joey Smith CC: internals@lists.php.net References: <4E3E0155.5050702@lerdorf.com> <20110809064549.GC21131@joeysmith.com> In-Reply-To: <20110809064549.GC21131@joeysmith.com> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Coverity Scan From: rasmus@lerdorf.com (Rasmus Lerdorf) On 08/08/2011 11:45 PM, Joey Smith wrote > A lot of the 'STACK_USE' ones seem to be false positives; it's reporting > when the stack "exceeds the maximum single use of 1024 bytes" - that 1024 > is a Coverity-configurable value which defaults to 1024. Yup, we can simply mark those as intentional/ignore although it wouldn't be a bad idea to have a quick look at each one to see if we really need to chew up 1k of stack on each of those occasions. People using PHP in embedded systems would appreciate that, I bet. -Rasmus