Community
Participate
Working Groups
When I start a debug launch for the first time in a clean workspace and hit a break-point in a Thread which has a monitor lock, then on the debug view it selects both the running JDIThread and the first element in JDIStackframe . Because of this wrong selection, the Expressions don't evaluate in the expressions tab. Steps to reproduce the issue: 1> Start Eclipse with a clean workspace. 2> Create a Java project (from Java perspective). 3> Create a class with main method(with a synchronized lock) as shown below: public class TestClass { public static void main(String[] args) { synchronized (new TestClass()) { String str = "Test String"; System.out.print("tests"); // line A } } } 4> Add a debug point at system.out line (line A). 5> Start debug as -> Java application . 6> As we hit the breakpoint for the first time, we get a popup to switch to debug perspective and we switch to Debug perspective. 7> Now we can see in debug view, both the JDIThread and the JDIStacktrace selected. 8> Notice that the Variables view is empty. (where as it is supposed to have an entry for the variable "str") 9> This happens only for the first breakpoint hit and first debug launch.With later breakpoints, the debug view selection is only on JDIStackframe and hence Variables view shows variables fine. Note: The issue can be reproduced, by closing the debugview and starting the debug launch again and on hitting the first breakpoint.
I see it happening in 4.7 as well. As it does not block any behavior and we can select the TestClass in the stackframe to see the variables, it can not be Critical.
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.