Community
Participate
Working Groups
When I double click in the breakpoints bar against the side of a method declaration, and run in the debugger, the breakpoint doesn't fire. If I put a breakpoint by the first statement in the method, it does fire: o public static void main(String args[]) { System.out.println("No debugger"); } public static void main(String args[]) { o System.out.prointln("Debugger fired"); } Can this be changed so that double-clicking against the method definition either fires the debugger, or moves the debug breakpoint to tne next available method?
There are several bugs in this area. Not committed to fix for 2.1 - marking as later.
This also happens when the breakpoint is at a commented out line as well. I put in a breakpoint at a line with a statement (which fired the debugger) and then wanted to comment out something for testing purposes. I later discovered that the line I had commented was the one with the breakpoint in, with the result that the debugger never fired that breakpoint.
*** Bug 36513 has been marked as a duplicate of this bug. ***
Marking as dup.
*** This bug has been marked as a duplicate of 1591 ***