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.
Product Version: NetBeans IDE Dev (Build 20081007032925) Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b13 System: Linux version 2.6.22-15-generic running on i386; UTF-8; en_US (nb) The watches are always evaluated to 'unknown type' and local variables are not shown in local variables window when debugging String.indexOf(char[] source, int sourceOffset, int sourceCount,char[] target, int targetOffset, int targetCount, int fromIndex) method Steps to reproduce: 1) debug code: String a = "abcdefghijklmnop"; String b = "defa"; boolean c = a.contains(b); 2) use step into to get to mentioned method
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.