Community
Participate
Working Groups
Build 20020321 There doesn't appear to be any way to set a breakpoint in source code which is not managed by Eclipse. I'm debugging code on a remote VM. The program includes some code which is managed by my workspace, and some which is found in external JARs. When I click on a stack frame for one of these unmanaged methods, I get a dialog asking where to find the source. I point the dialog at the source, and an editor on the appropriate .java file opens. However, I can't set breakpoints in this file: - there is no ruler displayed, so I can't double click o nthe ruler - the context menu's Add->Breakpoint action is disabled This is frustrating, as I'd like to set breakpoints in the code that I'm examining!
*** Bug 13841 has been marked as a duplicate of this bug. ***
This is more than a debug issue. The java debug API supports breakpoints in external files (since breakpoints are name based), but the java editor would need to support setting those breakpoints (i.e. a ruler is needed for external files, and support to recognize markers associated with an external file). Not sure this will be addressed in 2.0
Deferred for post 2.0
*** Bug 19410 has been marked as a duplicate of this bug. ***
As well, we should support breakpoint in "internal files" that are not on the buildpath.
Re-open for 2.1 investigation.
As a first step, what about a simple dialog where the user can enter a fully qualified type name and a line number to set a breakpoint?
I have an implementation of breakpoint creation/location verification that uses the JDOM. The problem is that it is slow in large compilation units (the JDOM takes seconds to build on larget CUs such as java.lang.Character). Not clear if this solution is going to be feasible. Moving to M5.
*** Bug 22958 has been marked as a duplicate of this bug. ***
Breakpoint in external source has been deferred for post 2.1 consideration.
*** Bug 32729 has been marked as a duplicate of this bug. ***
*** Bug 35308 has been marked as a duplicate of this bug. ***
Re-opening for 3.0
Released the first part of this feature. It allows to set line breakpoint ('standart') breakpoint in external files and files not in the classpath. It uses JDOM to find the name of the class and to verify the location of the breakpoint (see bug 1591 for more details). The same work need to be done for method breakpoints and watchpoints.
Method breakpoints in external source will be limited to 'simple' methods. Method breakpoints require the complete signature of the method, in the case of source files not in the classpath, this signature can be generated if it contains only primitive types. The real name of the non-primitive type cannot be resolved, there is no context to resolve them.
Released code to manage watchpoint in external files and files not in the classpath.
Released code to manage method breakpoint in external files and files not in the build path.
Please verify, Darin W.
Verified
