Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13683 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33427 invoked by uid 1010); 2 Nov 2004 12:57:14 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 33399 invoked from network); 2 Nov 2004 12:57:13 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by pb1.pair.com with SMTP; 2 Nov 2004 12:57:13 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iA2CvDPA004390 for ; Tue, 2 Nov 2004 07:57:13 -0500 Received: from radish.cambridge.redhat.com (radish.cambridge.redhat.com [172.16.18.90]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iA2CvCr16473 for ; Tue, 2 Nov 2004 07:57:12 -0500 Received: from radish.cambridge.redhat.com (localhost.localdomain [127.0.0.1]) by radish.cambridge.redhat.com (8.12.10/8.12.7) with ESMTP id iA2CvBBs024468 for ; Tue, 2 Nov 2004 12:57:11 GMT Received: (from jorton@localhost) by radish.cambridge.redhat.com (8.12.10/8.12.10/Submit) id iA2CvBNU024467 for internals@lists.php.net; Tue, 2 Nov 2004 12:57:11 GMT Date: Tue, 2 Nov 2004 12:57:11 +0000 To: internals@lists.php.net Message-ID: <20041102125711.GA24461@redhat.com> Mail-Followup-To: internals@lists.php.net References: <1306491163.20041101111627@marcus-boerger.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1306491163.20041101111627@marcus-boerger.de> User-Agent: Mutt/1.4.1i Subject: Re: [PHP-DEV] "Function registration failed" warning in current HEAD From: jorton@redhat.com (Joe Orton) On Mon, Nov 01, 2004 at 11:16:27AM +0100, Marcus Boerger wrote: > Hello Sebastian, > > Monday, November 1, 2004, 10:43:50 AM, you wrote: > > > PHP Warning: Function registration failed - duplicate name - > > next in Unknown on line 0 > > how about providing the backtrace when you set a breakpoint > in the error handler? Dumping the right variables from the > trace you can see which class is the root of the problem. Ah, just saw this mail - it's the InfiniteIterator class in SPL which is causing the warning. joe