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.
I'm writing a CharsetDecoder and repeatedly get NPEs trying to use a tooltip on a highlighted expression. I'll attach both the stack trace and java file in a moment. I have 2 breakpoints set, one at line 85 and one at 96. I've run to the one at 85. Steps to duplicate: 1. Set line breakpoints at lines 85 and 96. 2. Run the project (project will stop at bp on line 85). 3. Highlight "Character.isDigit(bytes[i + 1])" and move the mouse over the selected text I get a repeatable NPE from the jpda evaluator.
Created attachment 49601 [details] Stack trace
Created attachment 49602 [details] Source file being debugged
FYI, I'm using a private build which was updated and freshly compiled last night. I'm using JDK 1.5.0_12 on Solaris x86.
Reproduced. This is not really a regression from prior versions, trying the same in NB 5.5.1 does not throw an exception, but writes: Cannot call method "isDigit" in class "java.lang.Character". The call is ambigous. The evaluator algorithm seems to be confused by two methods: Character.isDigit(int) and Character.isDigit(char). Looking at Evaluator.java:1053, the "fix" to get the behavior of NB 5.5.1 is easy. However proper fix if this is more complicated. Since there are many more situations in which the evaluator does not work, I've created an umbrella issue #108873 and I would like to solve them all by a complete rewrite of the evaluator algorithm. However, this does not seem to be doable into NB 6.0, unfortunately. Changing to P3, since this is on the same level with other evaluator issues listed at http://www.netbeans.org/issues/showdependencytree.cgi?id=108873
The NPE is fixed, however it still does not evaluate the expression. :-( /shared/data/ccvs/repository/debuggerjpda/src/org/netbeans/modules/debugger/jpda/expr/Evaluator.java,v <-- Evaluator.java new revision: 1.37; previous revision: 1.36
Fixed in the new evaluator algorithm - see issue #108873.
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.