Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19780 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42712 invoked by uid 1010); 28 Oct 2005 13:37:50 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 42697 invoked from network); 28 Oct 2005 13:37:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Oct 2005 13:37:50 -0000 X-Host-Fingerprint: 194.109.193.120 unknown Linux 2.4/2.6 Received: from ([194.109.193.120:41869] helo=mx1.moulin.nl) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id E4/A9-57990-EA922634 for ; Fri, 28 Oct 2005 09:37:50 -0400 Received: from localhost (localhost [127.0.0.1]) by mx1.moulin.nl (Postfix) with ESMTP id 14BE8176019; Fri, 28 Oct 2005 15:37:51 +0200 (CEST) Received: from mx1.moulin.nl ([127.0.0.1]) by localhost (moulin [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19516-19; Fri, 28 Oct 2005 15:37:45 +0200 (CEST) Received: from [192.168.1.16] (bspr.xs4all.nl [194.109.161.228]) by mx1.moulin.nl (Postfix) with ESMTP id 99352175FDF; Fri, 28 Oct 2005 15:37:45 +0200 (CEST) Message-ID: <436229A2.1000202@iamjochem.com> Date: Fri, 28 Oct 2005 15:37:38 +0200 User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Hall Cc: PHP-DEV References: <20051028140325.BFE8.MIKE.HALL@twistdigital.co.uk> In-Reply-To: <20051028140325.BFE8.MIKE.HALL@twistdigital.co.uk> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at moulin.nl Subject: Re: [PHP-DEV] No error output? From: jochem@iamjochem.com (Jochem Maas) Mike Hall wrote: > Every developer at my company has experience this problem too, at one > point or another. We get it with Apache 1.3 and PHP 5.x. We've been > unable to figure it out. I thought I had it tied down to the gzip > output compression at one stage. But then it suddenly started working > okay and I couldn't get it to break again. I have problems like this on a regular basis in big/complex (well by my standards anyway) codebases that have heavy php5 oo in them. no errors _anywhere_ if I have a parse error or a require_once statement fails, I havbe had the problem since php5beta3 (when I started using php5) and have seen it happen on every version of php5 upto 5.0.4 (the highest version I have used properly) on windows, debian, redhat and gentoo using apache and apache2. basically AFAIC there is something wrong _deep_ in the engine but given that I have no idea how to prove this or provide any kind of short reproduce script I'm left to live with it ... it may of course be a problem with my code, I'm thinking a possible reference related segfault issue (and/or maybe __autoload() related). Actually IIRC Derick Rethans has posted before about issues he has had where problems were not easily (or at all) reproducable in a short script. (excuses to Derick if I misquote/misremember what he wrote in the past) actually this is one of the main reasons I read internals@ - in the hope someone might offer information that will help me either fix this issue in my code, expose a real engine problem or possibly give some inspiration as to how to track down the problem. ... I just wish I had the skills to work this problem :-) seeing as I don't I live with it and whenever I am faced with a blank page I know exactly what to do ... find the parse error and if there is none check every require statement in the files I have just changed... a process that alweays starts with this one liner: find . -name \*.php \! -exec php -l {} \; > > Mike > > > On Fri, 28 Oct 2005 13:52:31 +0100 > Marcus Bointon wrote: > > >>I'm running a recent snap of 5.1 with apache 2.0.54 (from fink) and >>MySQL 5.0.15 on OS X 10.4.2. For the last few days I've noticed that >>I'm getting no error messages out at all, neither to the browser nor >>to the server log. I have display_errors, log_errors and >>log_startup_errors set to On, error_reporting set to E_ALL | >>E_STRICT, but I'm seeing nothing on web output - a simple syntax >>error results in a blank page, e.g. >> >>>sdfsdf >>?> >> >>gives a blank page and nothing in server log. It produces an expected >>E_NOTICE error on a CLI version, so the problem is either in apache >>or the PHP apache2filter module. My apache setup has not changed >>recently whereas PHP has, so I'm looking there. >> >>I've reconstructed my php.ini and httpd.conf files from scratch so >>I'm pretty certain the settings in there are all ok. I did have >>latest xdebug installed, but I'm still seeing this with it disabled. >> >>As you might imagine, it's making debugging quite difficult. Has >>anyone else seen this problem? I can't find a bug report that looks >>like this. >> >>Marcus >>-- >>Marcus Bointon >>Synchromedia Limited: Putting you in the picture >>marcus@synchromedia.co.uk | http://www.synchromedia.co.uk >> >>-- >>PHP Internals - PHP Runtime Development Mailing List >>To unsubscribe, visit: http://www.php.net/unsub.php > > > Mike Hall > Twist Digital Media > e. mike.hall@twistdigital.co.uk > > D I S C L A I M E R > Statements and opinions expressed in this e-mail may not represent those > of the company. > > The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review, retransmission, dissemination or other use of, or > taking of any action in reliance upon, this information by persons or > entities other than the intended recipient is prohibited. If you > received this in error, please contact the sender immediately and delete > the material from any computer. >