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.
Summary: | Watches and local variables window does not work | ||
---|---|---|---|
Product: | debugger | Reporter: | Jiri Prox <jiriprox> |
Component: | Java | Assignee: | Daniel Prusa <dprusa> |
Status: | CLOSED FIXED | ||
Severity: | blocker | Keywords: | USABILITY |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jiri Prox
2008-10-08 15:25:46 UTC
reproduced on: Product Version: NetBeans IDE Dev (Build 200810080201) Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b14 System: Windows Vista version 6.0 running on x86; Cp1250; cs_CZ (nb) In my case all variables newly declared in jdk classes are affected. I understand that this is very confusing. But it's NOT a functional bug. Local variables can not be seen, because JDK sources are not compiled with local variable information ("-g:vars" or "-g" switch to javac is necessary to have variable information). Therefore debugger has no way to find their values. But the confusion is made by showing the parameters to methods. Since JDK 1.6 we can use StackFrame.getArgumentValues() call, which returns the arguments regardless of the compiler information. Therefore we present parameters, but can not present local variables defined in the body of the method. We should indicate this somehow. Therefore decreasing the priority to P3 and leaving this as a usability defect. Fixed, "Variable info not available" warning will be displayed in Variables view now. http://hg.netbeans.org/main/rev/501aa94984c7 Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier. |