Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 231342

Summary: Source lookup fails when debugging with target weaving
Product: [Eclipse Project] JDT Reporter: Curtis Windatt <curtis.windatt.public>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: darin.eclipse
Version: 3.4   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Curtis Windatt CLA 2008-05-09 13:42:40 EDT
Use a build that supports target weaving (M7 or later).
1) In your host, have one or more plugins
2) Launch a runtime workbench
3) In the runtime workbench, create or import a plugin that depends on one of the plugins in the host workspace
4) You should be able to open the class files with source under the Plug-in dependencies of your plugin in the runtime workbench.
5) Add a breakpoint somewhere inside your plugin that will allow us to step into code from one of the plugins in your host workspace.
6) Debug another runtime workbench
7) When you are at the breakpoint, step into code from the host workspace plugin
8) Source lookup fails

Reason:

In JavaSourceLookupUtil we are given the classpath entry that we need source for.  Debug is unable to get a java project for the classpath entry.  Without the project we cannot get the package fragment root and use JDT core's source lookup utility.  We revert back to using debug's generic DirectorySourceContainer, with subfolders turned off.  This fails because the source is in a src, src-ant, etc. subfolder.  Turning on the boolean flag to search subfolders is a workaround, but doing so might affect other users of debug.
Comment 1 Eclipse Genie CLA 2018-11-26 15:41:14 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.