Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100015 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82639 invoked from network); 22 Jul 2017 17:35:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jul 2017 17:35:09 -0000 X-Host-Fingerprint: 62.251.31.78 monitor.xs4all.nl Received: from [62.251.31.78] ([62.251.31.78:8394] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E5/52-02884-CCC83795 for ; Sat, 22 Jul 2017 13:35:09 -0400 To: internals@lists.php.net Date: Sat, 22 Jul 2017 19:35:05 +0200 Message-ID: References: X-Newsreader: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Posted-By: 62.251.31.78 Subject: Re: [PHP-DEV] Re: PHP 7.2.0 Beta 1 released From: phpdev@ehrhardt.nl (Jan Ehrhardt) Rasmus Lerdorf in php.internals (Sat, 22 Jul 2017 09:22:07 -0400): >Ok, so it is a normal E_WARNING and not the source of the fatal error you >hit. You must have something else going on. Perhaps a custom error handler >turning it into a fatal, although that also hasn't changed from 7.1. Drupal7 has a custom error handler, but I did not expect it to differ from PHP 7.1 to 7.2. But apparently, it does. Will dig deeper. As a side note: I could reproduce the fatal error on a CentOS6 machine with PHP 7.2.0 Beta 1, so it is not Windows-only. -- Jan