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 have tried to set breakpoint in the innerclass of a innerclass. The breakpoint was marked as (valid == false) and also the class was wrongly set to the outer inner class. After correcting the class property everything worked ok. It is quite annoying because you set a breakpoint to the System.out line and the text get printed but the debugger will not stop.
Note: the inner inner class is anonymous. In this situation it happens always.
Assigned
Assign
Version: 'Dev' -> 3.2
Fixed together with bug #8984 (Breakpoint set to a line in innerclass of a innerclass is not valid).
I am still able to reproduce this bug in Pilsen (build 010321). Steps to reproduce: * Put breakpoint into anonymous inner class of named inner class. * Compile the source file with Javac. Generated class files will be <someclass>.class, <someclass>$<namedInnerClass>.class and <someclass>$1.class. * The debugger will not stop on that breakpoint. Note: If you try to compile it with FastJavac (the IDE's default compiler) you will get class files <someclass>.class, <someclass>$<namedInnerClass>.class and <someclass>$<namedInnerClass>$1.class and the breakpoint will work.
Fixed (main trunk, release32) The fix is not as nice as it could be because of the JDK bug #4431170. Source code of LineBreakpoint.java (both in JPDA and tools debugger) may be polished in the future when the JDK bug is fixed. If the breakpoint is set to an anonymous class, its "Source Name" property can't never be set to proper name - just because it is anonymous. There is no standard way how to compute the name of the generated .class file from the source code for anonymous classes.
Verified in Netbeans release 3.2 build 21.
Target milestone -> 3.2
Resolved for 3.3.x or earlier, no new info since then -> closing.