ID: 34009
Updated by: [EMAIL PROTECTED]
Reported By: ast at gmx dot ch
Status: Bogus
Bug Type: Scripting Engine problem
Operating System: Gentoo Linux
PHP Version: 4.4.0
New Comment:
No, whatever you may think all test cases do NOT have E_ALL set.
The two phpinfo URLs listed under your "Unexpected result observed on"
have error_reporting = E_ALL (2047).
The URL listed under "Correct behaviour observed on" has
error_reporting set to 2039 (E_ALL ^ E_NOTICE).
It's a Notice. You get it when E_NOTICE is enabled and not when it
isn't. QED
(And yes, I personally think it's a correct Notice; the return line
should be "return &$false" to not get a Notice, surely? But maybe I'm
wrong about that....)
Previous Comments:
------------------------------------------------------------------------
[2005-08-08 12:58:48] ast at gmx dot ch
[EMAIL PROTECTED]:
So you say with error_reporting = E_ALL it *should* give a Notice in
this case?
If so, no offence, but I think you haven't read the bug report
carefully. All tested systems have error_reporting E_ALL. The point is
that even with E_ALL, it doesn't give a Notice on most systems (and I
think that's correct), but others do.
But we're now at a point where we think that 3rd party extensions
could be responsible for the incorrect behavior.
------------------------------------------------------------------------
[2005-08-08 12:51:54] [EMAIL PROTECTED]
There's no fault in the code or PHP. It's the server setup differing.
(Strong Hint: look at the value of error_reporting on each of the
phpinfo pages you quoted.)
------------------------------------------------------------------------
[2005-08-08 10:48:38] ast at gmx dot ch
John Lim from the adodb project wrote the following:
> There is nothing wrong with this code.
>
> I have found this problem normally occurs when php 4.4 is
> being run with an old version of zend optimizer or similar
> 3rd party software.
Also, one of the ISPs that can reproduce this incorrect behavior said
they've compiled PHP statically, but zend was DSO. They use the same
PHP on multiple boxes and only on one they can reproduce this issue.
I'll notify them about the statement from John Lim, probably that's
it.
If that's the case, the bug is indeed invalid. But it's good to know
what can cause this issue.
------------------------------------------------------------------------
[2005-08-07 14:32:58] ast at gmx dot ch
1. Do we agree that PHP 4.4.0 should not show a notice in this case?
2. I know that it's nearly impossible to debug a problem if you can't
reproduce it on your own machine. So I understand your point of view.
But I see 3 different hosts, all different providers, that show the bug
in PHP 4.4.0.
I come to the conclusion that something must be really wrong.
I hope we can get one of the providers to install the current CVS
version of PHP 4.x. But maybe we can only offer you SSH access to a PHP
4.4.0 installation that shows the bug.
------------------------------------------------------------------------
[2005-08-07 14:24:24] [EMAIL PROTECTED]
Your failure to try the snapshots is not our problem. It works like it
should work on all the servers I've tried it on.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/34009
--
Edit this bug report at http://bugs.php.net/?id=34009&edit=1
