Bug #16065: var_dump() infinite loop. Problem occured after today's patch(np w/ 4.1.2)

From: Date: Thu, 14 Mar 2002 14:26:23 +0000
Subject: Bug #16065: var_dump() infinite loop. Problem occured after today's patch(np w/ 4.1.2)
Groups: php.bugs 
Request: Send a blank email to php-bugs+get-2479@lists.php.net to get a copy of this message
From: ahristov@icygen.com Operating system: RH 7.1 PHP version: 4.0CVS-2002-03-14 PHP Bug Type: Arrays related Bug description: var_dump() infinite loop. Problem occured after today's patch(np w/ 4.1.2) <?php //ob_start(); $a=array(); $a[]=&$a; array_pop($a); var_dump($GLOBALS); //ob_end_flush(); ?> This piece of code causes infinite loop. If the commments are removed than this little scripts starts to eat memory too fast. 100MB for 15secs. When the physical RAM was not available started to eat from the swap. If var_export() is used no problems(with the CVS). With 4.1.2 only causes Fatal Error - too deep recursion. Proably this has something with Yasuo's patch that tried force var_dump() to work like print_r() - showing recursion not just crashing. -- Edit bug report at http://bugs.php.net/?id=16065&edit=1 -- Fixed in CVS: http://bugs.php.net/fix.php?id=16065&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=16065&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=16065&r=needtrace Try newer version: http://bugs.php.net/fix.php?id=16065&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=16065&r=support Expected behavior: http://bugs.php.net/fix.php?id=16065&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=16065&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=16065&r=submittedtwice

« previous php.bugs (#2479) next »