Community
Participate
Working Groups
Eclipse 4.5 N20150216-2000. - Take the following example and press Ctrl+Shift+O to invoke 'Organize Imports' dialog after setting a breakpoint at the first line of org.eclipse.ui.dialogs.AbstractElementListSelectionDialog.getSelectedElements(): package com.test; public class A1 { Map<String, List<Document>> files; } - When the breakpoint is hit, select 'fFilteredList' and press Ctrl+Shift+I to inspect the value of 'fFilteredList'. I get the message: "Evaluations must contain either an expression or a block of well-formed statements". Hovering over "fFilteredList" shows the value 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.
Still reproducible with 4.16 latest build.
Strange, hover works but not inspect.
Seems like the problem is this variable is inside the org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine.getCompiledExpression(String, IJavaStackFrame) this reference. And these reference variables are treated as outer class variables. And these variables are only added to the evaluation engine if they are prefixed with val$. A fix would be to include all variables that we find in this reference in the evaluation engine.
This works in variable hovering because we have a different logic in how variable hovers are handled. In hovering we read the variables from the current stackframe.
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.
