Menu
Eclipse allows running an application in Debug mode which helps with stepping through each line of code in a program. Eclipse also provides a Debug Perspective which is a set of views grouped together that help inspect code and make the debugging process very effective.
The solution was to enable it again, start a debug session, the breakpoint is hit and shown in the UI, then disable again the option. There is also another simpler way that will make Eclipse show the debugging highlight at the breakpoint or rather refresh the debugging UI to work as it should.
Variables/Expression view – Shows the declared variables and their values. Press Ctrl+Shift+d or Ctrl+Shift+i on a selected variable or expression to show its value. You can also add a permanent watch on an expression/variable that will then be shown in the Expressions view when debugging is on.
It looks like the problem is related to the new debug feature "Show method result after a step operation": See the thread Eclipse Oxygen - Debugging Issue on the Eclipse forum:
The workaround is to go to Preferences -> Java -> Debug and disable the option "Show method result after a step operation (if supported by the VM; may be slow)".
See also the bug report in the Eclipse Bugzilla Bug 531706 - Oygen.2 com.sun.jdi.InternalException: Got error code in reply:35 while debugging
I have also faced with same issue on local server.
But, it was the issue of for loop.
I was using:
for(Object obj: list)
{
for(Object obj2 : list)
{}
}
When I replaced that code by simple for loop (index based), it resolved the above issue. I think for each loop not able to iterate another list of same Type in same loop. Work around for this is replace that for loop to index based for loop.
Just to be sure: are you remote debugging some instrumented code ?
Because there seem to be some problems with JProfiler...
If you have the "Logical Structures" turned on in the Expressions tab while debugging, this seems to still cause issues even in Eclipse IDE version 4.11.0. Turning it off helped me. It is not a "solution" per se rather a work-a-around.
See the Eclipse Bug 48815
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With