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

Bug 505327

Summary:

Debug expressions broken when source is located in OSGI-OPT/src of JAR

Product:

[Eclipse Project] JDT

Reporter:

Marc Schlegel <marc.schlegel>

Component:

Debug

Assignee:

JDT-Debug-Inbox <jdt-debug-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

major

Priority:

Version:

4.6

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

stalebug

Attachments:

Description	Flags
Screenshot showing expression failure in Watch/Display view	none

Description Marc Schlegel

2016-10-07 03:13:57 EDT

Created attachment 264683 [details]
Screenshot showing expression failure in Watch/Display view

Eclipse provides a feature where sources for a artefact (osgi-bundle) can be placed inside the artefact under OSGI-OPT/src. The debugger is able to pick the sources without having to handle source-attachments in the BuildPath.

This feature is heavily used by the BndTools/OSGi community.

Currently when setting a breakpoint within a module which has its source included under OSGI-OPT/src, the debugger stops at the correct location and displays all variables.
Now it is not possible to evaluate any expression! Adding a watch-expression based on a current variable fails as does any expression in the Display-view.

Furthermore there is no content-assist for anything beyond the currently available variable.

Please see attached screenshot. The example was done with the latest MyFaces-Impl from Maven (debug information is available) which was enhanced with sources.

BndTools does nothing special about the debugger. They completely rely on the feature provided by Eclipse (see discussion here: https://groups.google.com/forum/#!topic/bndtools-users/zn6x8lOjCms)

Comment 1 Eclipse Genie

2019-09-10 07:11:13 EDT

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.