Community
Participate
Working Groups
Created attachment 244753 [details] debugger behavior I'm debugging an Eclipse RCP application. I'm using OS X 10.9.4 with Java 8 installed. Since upgrading to 4.4 I've noticed that the debugger intermittently fails to display the current source location. Selection any line of the stack frame does not switch to the editor window for that class. Other views, such as the variables view seem to still work ok. Selecting "Lookup source" from the context menu does display the line marker, however as soon as I step then marker disappears again. The attached screenshot shows the selected stackframe, but no current line marker is displayed in the editor.
I have the exact same behavior on Kubuntu 15.04, Eclipse 4.4.2 and Java 8 while debugging a Java EE application on Tomcat.
I'm having the same problem: Eclipse 4.4.2.M20150204-1700 jdk1.8.0_45 64-Bit Windows 7 Are you also running a 64-Bit Java/Eclipse? Not sure but I think this started after I switched to 64-Bit.
I have the same problem on Eclipse Mars - Integration Build (JDK 8u25 64 bit, Windows 7).
Adding to comment #1, I also use a 64 bit JDK. However, this problem stopped hapenning after a reboot on the same day.
After removing org.eclipse.jdt.* and org.eclipse.debug.* plugin's workspace cache it's working.
Probably [Bug 454028|https://bugs.eclipse.org/bugs/show_bug.cgi?id=454028] is related to this. Maybe I had some invalid cache data from before the patch for 454028 and that's why after removing this cache it's working properly.
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.
The bug is still relavant - I am experiencing it with : Version: 2022-09 (4.25.0) Build id: 20220908-1902 On Windows 7. I have the latest updates applied.
