|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2005-01-19 22:10 UTC] sniper@php.net
[2005-03-07 21:41 UTC] sniper@php.net
[2005-03-15 01:00 UTC] php-bugs at lists dot php dot net
[2005-04-01 08:33 UTC] john at carney dot id dot au
[2005-04-01 08:35 UTC] john at carney dot id dot au
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Fri Oct 24 06:00:01 2025 UTC |
Description: ------------ Since php 5.0.1, extract($GLOBALS, EXTR_REFS) seems to corrupt code memory and cause various random problems. In my test case, it caused COM("someobject") to always return null, and in another case it just caused some strange output of a "1" instead of the expected strings. I never had a problem in php 5.0.0 up to CVS snapshot php5.0-win32-200407301630. Commenting out extract($GLOBALS, EXTR_REFS) fixes all strange behavior. I had a similar problem in php 4 which I reported as bug id 25708. That bug was fixed and I never had a problem again until 5.0.1. Reproduce code: --------------- extract($GLOBALS, EXTR_REFS); $query = new COM("IXSSO.Query"); if(is_object($query) == false) { var_dump($query); print "Can't create IXSSO Query object."; exit(); } Expected result: ---------------- Nothing Actual result: -------------- PHP has encountered an Access Violation at 01D5F185