ID: 31753
Updated by: [EMAIL PROTECTED]
Reported By: t3 at rohms dot com
-Status: Open
+Status: Bogus
Bug Type: Variables related
Operating System: FreeBSD 4.3
PHP Version: 4.3.10
New Comment:
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same.
Thank you for your interest in PHP.
See #30074, #31217.
Previous Comments:
------------------------------------------------------------------------
[2005-01-29 20:14:41] t3 at rohms dot com
Description:
------------
I have an application that up until 4.3.10, worked perfectly with no
modifications; upon installing 4.3.10, one part of the application no
longer functions properly. I have narrowed down the problem to an area
involving the use of the statement:
extract($GLOBALS,EXTR_REFS);
in association with running eval() on a code block. If the code within
that EVAL'd code block calls a subroutine, the passed parameter data is
horribly messed up -- some kind of stack issue.
I have verified this is a new anomoly that is the result of the latest
version upgrade. However, I believe this may be related to the zend
engine and not php. When my system broke, I reverted php back to 4.3.6
and it still wasn't fixed; only when I reverted back to 4.3.6 and
removed the references to the newest version of the zend did the
problem disappear.
Reproduce code:
---------------
I will be working on some sample code, but right now I've had to revert
php back to an earlier version to make about a half-dozen sites
functional.
The problem appears in some code I've written which involves storing
blocks of php code in MySQL and EVAL'ing them. I created a subroutine
that pulls a record from the database and EVAL's it. Because it's a
subroutine I use the extract($GLOBALS,EXTR_REFS); before I eval the
code so that the code has access to globals. Everything works fine
UNTIL something in that code calls a function... the data passed to the
function is completely screwed up. This only appears to happen in
4.3.10 with the new version of zend.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=31753&edit=1
