Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:7591 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 64334 invoked by uid 1010); 4 Feb 2004 22:18:52 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 64275 invoked from network); 4 Feb 2004 22:18:51 -0000 Received: from unknown (HELO mail.internet-factory.de) (62.134.147.34) by pb1.pair.com with SMTP; 4 Feb 2004 22:18:51 -0000 Received: from pharao.lammfellpuschen.de (pD95266B4.dip.t-dialin.net [217.82.102.180]) by mail.internet-factory.de (8.12.8/8.12.8) with SMTP id i14MIcJP015555; Wed, 4 Feb 2004 23:18:38 +0100 Received: by pharao.lammfellpuschen.de (sSMTP sendmail emulation); Wed, 4 Feb 2004 23:18:37 +0100 Date: Wed, 4 Feb 2004 23:18:37 +0100 To: Rasmus Lerdorf Cc: internals@lists.php.net Message-ID: <20040204221837.GJ29892@pharao.serveftp.org> Reply-To: messju mohr References: <20040204215030.3755.qmail@pb1.pair.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-WebServ-MailScanner-Information: Please contact the ISP for more information X-WebServ-MailScanner: Found to be clean X-WebServ-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.922, required 5, AWL -3.36, BAYES_00 -4.90, RCVD_IN_DYNABLOCK 2.60, RCVD_IN_NJABL 0.10, RCVD_IN_NJABL_DIALUP 3.54, RCVD_IN_SORBS 0.10) Subject: Re: [PHP-DEV] Re: -d stopped working in 4.3.4? From: messju@lammfellpuschen.de (messju mohr) On Wed, Feb 04, 2004 at 02:13:59PM -0800, Rasmus Lerdorf wrote: > On Wed, 4 Feb 2004, Joe Estock wrote: > > > On 2/4/2004 3:12 PM, Rasmus Lerdorf wrote: > > > Is it me or does -d no longer work in 4.3? To test: > > > > > > php -d "track_errors=1" -i | grep track > > > > > > (assuming you have it off in your php.ini) > > > > > > Works fine for me in 4.3.2 but looks quite broken in 4.3.4. Anybody play > > > around in that code? > > > > > > -Rasmus > > > > Works fine for me in 4.3.4RC3. Here is the output: > > > > php -d "track_errors=1" -i | grep track > > track_errors => Off => Off > > Well that shows exactly that it didn't work. track_errors should be > saying On there since you set it to 1 with the -d. It turns out > that between PHP 4.3.2 and 4.3.4 php -i was changed to ignore any -d > settings. it works for me with php-4.3.4 cgi-sapi: track_errors is reported to be set correctly. but it doesn't work with cli-sapi (i only had 4.3.3 as cli to test that). it seems the problem is specific to the cli-sapi. > -Rasmus