Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96296 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29550 invoked from network); 9 Oct 2016 06:06:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Oct 2016 06:06:34 -0000 Authentication-Results: pb1.pair.com header.from=laruence@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=xinchen.h@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.216.177 as permitted sender) X-PHP-List-Original-Sender: xinchen.h@zend.com X-Host-Fingerprint: 209.85.216.177 mail-qt0-f177.google.com Received: from [209.85.216.177] ([209.85.216.177:36095] helo=mail-qt0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 90/D9-20821-36ED9F75 for ; Sun, 09 Oct 2016 02:06:30 -0400 Received: by mail-qt0-f177.google.com with SMTP id m5so37017858qtb.3 for ; Sat, 08 Oct 2016 23:06:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=F+YLm31249oR0cZCEN4Rgof1T2gxWGuhne9/PwbyNMU=; b=PX3jtgjcdYNtvScqZHfkef+9IunBMBFi33DdGzInbwNaZ3TGgcg4O4QAZYs6SAUGjt x1XZJJIYN0IbzlqAYjhtbz+Gr2Pfm60ZzjtN3vZxxCAqCBZEZZWF7vopeKnYENJ2ft/C jN8Z3quoclsPMh3QCnBAtP53Xhyx7pcxa7hqI3dcZopo5nD5lsjvBsRPNF7Kw/1pRCtt cwpIFKMRZa0OS0w4xS72m1paZ5qUqGSusZjgEqWxX+RAXjdVyfTauJP9ADwEn2I2xc63 Kfud2QTfvcw1CRH+hNSADwmadd07cKJfutXzcXMiXWXOLJDFJBAdvZgNrglpHTH+c619 Op5A== X-Gm-Message-State: AA6/9RnDML4HsIdpnFmS+Y6Kidx8+dJQMRn8Y/6nB9KDvo8YNICUhBN22dUpxQl7bLZioUbB X-Received: by 10.200.45.246 with SMTP id q51mr26328626qta.108.1475993185246; Sat, 08 Oct 2016 23:06:25 -0700 (PDT) Received: from mail-qk0-f179.google.com (mail-qk0-f179.google.com. [209.85.220.179]) by smtp.gmail.com with ESMTPSA id r57sm129107qtr.47.2016.10.08.23.06.24 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Oct 2016 23:06:24 -0700 (PDT) Received: by mail-qk0-f179.google.com with SMTP id f128so55124105qkb.1 for ; Sat, 08 Oct 2016 23:06:24 -0700 (PDT) X-Received: by 10.55.137.3 with SMTP id l3mr25208350qkd.128.1475993184430; Sat, 08 Oct 2016 23:06:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.163.65 with HTTP; Sat, 8 Oct 2016 23:06:03 -0700 (PDT) In-Reply-To: <010701d2218e$b2e12d60$18a38820$@belski.net> References: <010701d2218e$b2e12d60$18a38820$@belski.net> Date: Sun, 9 Oct 2016 14:06:03 +0800 X-Gmail-Original-Message-ID: Message-ID: To: Anatol Belski Cc: Davey Shafik , Nikita Popov , Derick Rethans , PHP Developers Mailing List Content-Type: multipart/alternative; boundary=94eb2c073df872f39c053e687163 Subject: Re: [PHP-DEV] Regression between RC1 and RC2? From: laruence@php.net (Xinchen Hui) --94eb2c073df872f39c053e687163 Content-Type: text/plain; charset=UTF-8 Hey: On Sun, Oct 9, 2016 at 2:06 AM, Anatol Belski wrote: > Hi, > > > -----Original Message----- > > From: me@daveyshafik.com [mailto:me@daveyshafik.com] On Behalf Of Davey > > Shafik > > Sent: Friday, October 7, 2016 10:05 PM > > To: Nikita Popov > > Cc: Derick Rethans ; PHP Developers Mailing List > > > > Subject: Re: [PHP-DEV] Regression between RC1 and RC2? > > > > Yes, we should not mask the exception. The behavior in 7.0/7.1.0RC1 is > much > > better IMO. > > > > (As seen here: https://3v4l.org/EJpD4#v700) > > > > - Davey > > > > On Fri, Oct 7, 2016 at 12:52 PM, Nikita Popov > wrote: > > > > > On Fri, Oct 7, 2016 at 9:31 PM, Derick Rethans wrote: > > > > > > > Hi, > > > > > > > > I was looking at Xdebug for PHP 7.1, and I ran into the following > > > > inconsistency: > > > > > > > > https://3v4l.org/tHteN > > > > > > > > I first thought that Xdebug was messing up, but it seems like it's > > > > different behaviour in PHP itself. As I clearly return an array from > > > > __debugInfo, I don't think the new result is the correct one. > > > > > > > > cheers, > > > > Derick > > > > > > > > > > This is due to https://github.com/php/php-src/commit/ > > > 2d8ab51576695630a7471ff829cc5ea10becdc0f, which landed in PHP-7.0 as > > well. > > > The problem is that __debugInfo currently is not able to handle > > > exceptions gracefully. I think we should revert this change for now as > > > it hides the fact that the underlying cause of the error is an > exception. > > > > As far as I understand the bug #73067, it was about avoiding the fatal > error, not about avoiding the exception. Please correct if I'm wrong. But > given this, the fatal error still persists while the exception is removed. > It looks like it's doing the exact reversed to what one would expect - no > fatal error and the exception can be catched. > > I see that it's not yet released in 7.0, so I would prefer to revert this > in the release, at least. Hui, Nikita, do you think it's possible to > improve this for 7.0 in a follow up? I would revert in 7.0.12 and there'll > be room to fix it in the dev branch till 7.0.13. Otherwise I'd suggest to > revert to the previous behavior in 7.0+ and do a fix in an appropriate > higher branch. > The real problem is: we are expecting __debugInfo always returns array, but it doesn't if exception is threw. so, if we keep the exception, then we need inserts checks for exception (no array) after every debugInfo is called, or, make a FATAL error like the way I did however, I think latter is better, but maybe we could improve the fatal error message: " Fatal error, __debugInfo must return an array, but an exception with " msg" is threw" thanks > > Thanks > > Anatol > -- Xinchen Hui @Laruence http://www.laruence.com/ --94eb2c073df872f39c053e687163--