Community
Participate
Working Groups
Build ID: 3.4 GA I20080617-2000 Steps To Reproduce: 1. Extract Eclipse Ganymede RCP build 2. Extract Windows RCP SDK and Delta Pack to another directory 3. Start Eclipse Ganymede RCP IDE 4. Set target platform to dir in step 2. 5. Create Hello World RCP app using wizard and accepting defaults. 6. Open Shell.class (Ctrl+Shift+T). This opens the "ClassFileEditor". 7. Put a breakpoint on first line in the open() method. You can see the little blue dot in the margin. 8. Debug the RCP application 9. Breakpoint is hit. Instead of taking me to the earlier Shell.class editor, a new editor is opened, a "CompilationUnitEditor". I do not see my blue breakpoint dot, I do not have Ctrl+Shift+I inspection*, and I am put in the middle of a comment in the solaris.gtk.sparc version Shell.java. More information: *Ctrl+Shift+I gives this error - "Unable to evaluate the selected expression: To perform an evaluation, an expression must be compiled in the context of a Java project's build path. The current execution context is not associated with a Java project in the workspace."
debugging overlords, any thoughts?
Possible dupe of bug 260850. The PDE Source lookup director had no way of knowing what fragment we were actually running. *** This bug has been marked as a duplicate of bug 260850 ***
I tried the steps on 3.5M6 with the same results (actually the carbon.macosx version came up this time, but it's effectively random). So...can this be reopened or is it a WONTFIX??
Needs more investigation.
This needs to be addressed before 3.5 is out the door.
This is also problematic if a team is trying to use a shared target platform and different team members are developing on different platforms. For example, most work on windows but some work on OS X, so both SWT source plug-ins are installed. But it is not predictable which one will be loaded by the debugger. This is almost a show-stopper for cross-platform development with a shared target platform.
This works for me using the latest I-build (I20090421-0930). Can anyone else verify this? I think it's a dup of bug 260850.
*** This bug has been marked as a duplicate of bug 260850 ***
Hi, i run into the same problem and were very happy to read that it has been fixed. so i have tried it with build I20090619-0625 and it ends with the same error -> "unable to evaluate the selected expression" any help on that? regards lukas
Needs investigation.
Eclipse 3.5.2 Build id: 20100218-1602 This bug is still not fixed and debugging of SWT classes doesn't work as expected if the target platform contains the delta pack ...
This works for me in 3.6, but *not* on 3.5.2
There does appear to be a bug here... Our original test case for bug 260850 dealt with hosts/fragments in the workspace. The code path here is different as the host/fragments are external. Needs more investigation.
Created attachment 164158 [details] patch
Applied/Fixed. Please verify, Curtis.
Verified.
