Bug 538916 - Java 5 source version shown for Java 8 class
Summary: Java 5 source version shown for Java 8 class
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.8   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-11 05:19 EDT by Ed Willink CLA
Modified: 2022-10-26 19:12 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2018-09-11 05:19:13 EDT
While debugging Bug 538771, I needed to single step UTF8Reader.class and was surprised to see that the source was misaligned. The debugger was displaying the Java 5 version although the Java 8 version was executing. Explicitly opening the Java 8 version enabled better progress to be made, but the debugger reverted to the Java 5 version with each single step.

I have not seen this before, but perhaps I haven't looked at JRE classes whose source had evolved. Perhaps it only occurs under the maven-surefire launch.

This occurred using 2018-09 RC1 contributions. I have distinct VMs for Java 5, 6, 7, 8 in my workspace, so some referenced bundles (such as EMF) have a Java 5 VM available for their J2SE-1.5 BREE. Perhaps maven-surefire with just one VM is incompatible with JDT debug that can see 4 VMs.
Comment 1 Sarika Sinha CLA 2018-09-11 05:32:17 EDT
Please provide a test case which can be reproduced with Eclipse SDK without maven.
Comment 2 Ed Willink CLA 2018-09-11 05:44:40 EDT
Will do if I see it for normal DT standalone usage, but I suspect maven-surefire is involved.
Comment 3 Eclipse Genie CLA 2020-09-02 16:07:14 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.
Comment 4 Eclipse Genie CLA 2022-10-26 19:12:18 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.