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 225163 - cannot search all (nested) local variables
Summary: cannot search all (nested) local variables
Status: NEW
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.2.1
Hardware: PC Windows 8 x64
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-22 04:18 UTC by whk22e
Modified: 2013-01-22 13:30 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description whk22e 2013-01-22 04:18:56 UTC
I am working on a php project (a drupal site) and if I want to see if I have a given value available at a breakpoint so I can use that value in my code.  I can search the values in the local variables pane by simply giving it focus and typing the value (say, 'test'). However, this search only searches visible variables and does not search nested variables. Therefore if I want to use 'test' in my code and it is defined in Object1->array1->object2-> etc  a search would never show that I have access to this value.  

Thanks, and thanks for the great IDE
Comment 1 Martin Entlicher 2013-01-22 13:30:13 UTC
This is a natural consequence of the implementation.

It's not possible to pre-load all nested variables each time the list of variables is loaded, since we would potentially retrieve a large number of values.

When you start typing, you expect some reasonable response. That response could not be guaranteed, if we load all nested variables asynchronously.

The amount of nested variables can be quite large and in theory, all objects that were created in the program might be loaded. That may result in not only CPU, but memory problems as well. If we would limit the depth, the search would not be reliable.

However, I agree that a search like this can be useful, thus I'm changing this to an enhancement. It would most probably have to be implemented as a special kind of search.