Community
Participate
Working Groups
Build Identifier: I20110310-1119 This issue was previously logged as Bug 126262 and marked as fixed but it is still reproducible if Variables View and Expressions View are both visible at the same time. Reproducible: Always Steps to Reproduce: 1. create a simple java project with a local variable and debug it 2. open Expressions View and move it in another place so the both Variables and Expressions views are visible at the same time 3. add the local variable in the Expressions View 4. change the variable's value from the Variables View (e.g. right-click the variable and select Change Value option) => you can observe that the value of the variables in Expression View remains unchanged.
Can you specify which debugger are you using (JDT, gdb with CDI, etc)? Refreshing the views in response to data change needs to be initiated by the debugger back end, so this is not likely a general Platform issue.
(In reply to comment #1) > Can you specify which debugger are you using (JDT, gdb with CDI, etc)? > Refreshing the views in response to data change needs to be initiated by the > debugger back end, so this is not likely a general Platform issue. Yes, I'm using JDT.
I logged this issue to platform because it is reproducible both with JDT and with CDI GDB. This issue was previously logged in platform as Bug 125783 and marked as fixed but it doesn't work if both variable and expression views are visible. In other words it only works if the Expressions View is redrawn after the variable was changed in Variables View. The issue was also logged in CDT as Bug 126262 and partially fixed, meaning that because of a platform issue (Bug 125783 ?), the variable change will not show up in Expressions View until the view is redrawn just like with JDT case.
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.
Works well with Build id: I20191111-1800
