Community
Participate
Working Groups
If the locations being compared in JDIThread.shouldDoExtraStepInto(Location) have the same default stratum line numbers (when the default stratum of the class is not Java) and are located in different source files (location.sourceName() is different) the shouldDoExtraStepInto incorrectly returns true causing an extra step to be performed when it should not. I think lineNumber(JAVA_STRATUM_CONSTANT) should be tested instead of checking the default stratum value. There appears to be a second instance of this in JDIThread.handlEvent for STEP_OVER.
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.
This is still an, I have checked the code I mentionned in JDIThread and it is still not referencing JAVA_STRATUM_CONSTANT so will still fail in the same way I described when a different default stratum is used.
This is still an issue, the methods have still not been fixed to specify JAVA_STRATUM_CONSTANT.
(In reply to Alan Staves from comment #4) > This is still an issue, the methods have still not been fixed to specify > JAVA_STRATUM_CONSTANT. If you are interested in a fix, please file the issue at https://github.com/eclipse-jdt/eclipse.jdt.debug/issues and propose a PR.
