This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 180998 - Infinite evaluation of array or class parameters in watches or variables
Summary: Infinite evaluation of array or class parameters in watches or variables
Status: RESOLVED DUPLICATE of bug 179533
Alias: None
Product: php
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: PC Mac OS X
: P2 normal (vote)
Assignee: rmatous
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-20 15:31 UTC by okhoma
Modified: 2010-02-22 06:55 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Test case (37 bytes, text/php)
2010-02-20 15:31 UTC, okhoma
Details
Netbeans messages.log (38.81 KB, application/octet-stream)
2010-02-20 15:32 UTC, okhoma
Details
xdebug.log (33.33 KB, text/plain)
2010-02-20 15:32 UTC, okhoma
Details
messages.log (69.64 KB, text/plain)
2010-02-20 15:44 UTC, okhoma
Details

Note You need to log in before you can comment on or make changes to this bug.
Description okhoma 2010-02-20 15:31:29 UTC
Created attachment 94359 [details]
Test case

Test case:

<?php
$test=array(0);
echo $test;
?>

Steps to reproduce:

1. Place breakpoint in attached index.php on line 'echo $test' (included above)
2. Run debugger - the execution will stop on the breakpoint
3. Switch to Variables window and inspect contents of $test variable
4. Variables window shows multiple '0' items in $test and number of items is constantly growing:

<> test           array
       <> [0]      integer      0 
       <> [0]      integer      0 
       <> [0]      integer      0 
        ...
Comment 1 okhoma 2010-02-20 15:32:10 UTC
Created attachment 94360 [details]
Netbeans messages.log
Comment 2 okhoma 2010-02-20 15:32:28 UTC
Created attachment 94361 [details]
xdebug.log
Comment 3 okhoma 2010-02-20 15:44:43 UTC
Created attachment 94362 [details]
messages.log
Comment 4 rmatous 2010-02-22 06:55:56 UTC

*** This bug has been marked as a duplicate of bug 179533 ***