Edit report at http://bugs.php.net/bug.php?id=52562&edit=1
ID: 52562 Updated by: fel...@php.net Reported by: nick at witthaus dot com Summary: Crash when using $GLOBALS -Status: Feedback +Status: Bogus Type: Bug Package: Reproducible crash PHP Version: 5.3.3 Block user comment: N New Comment: No problem, thanks for reporting anyway! ;) Previous Comments: ------------------------------------------------------------------------ [2010-08-07 18:58:49] nick at witthaus dot com Sorry, I had eAccelerator installed and that seemed to be causing the problem. I removed it and it worked as expected. I apologize for being an idiot. ------------------------------------------------------------------------ [2010-08-07 18:14:19] fel...@php.net Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php for *NIX and http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32 Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. I cannot reproduce this. Are you using some extension that touches in the engine? ------------------------------------------------------------------------ [2010-08-07 18:10:36] nick at witthaus dot com Description: ------------ There seems to be a crash in 5.3.3 when trying to access the value of a $GLOBALS array variable when there is another $GLOBALS variable is used as an index. This worked in 5.3.2. Test script: --------------- <?php $GLOBALS['foo'] = array('foo0','foo1'); $GLOBALS['bar'] = 0; echo $GLOBALS['foo'][$GLOBALS['bar']]; ?> Expected result: ---------------- I expect to see 'foo0' echoed. Actual result: -------------- Causes a crash in 5.3.3. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/bug.php?id=52562&edit=1
