Community
Participate
Working Groups
The fix for bug 317045 caused a ClassCastException in some cases, see bug 550631. This is due to not taking primitive types into account. We have added a cast for bug 550631, but this means there are still cases with synthetic primitive variables that are not being handled. I.e. cases for which bug 317045 is not yet fixed. The original fix: https://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=f73f194db9f438bd1a376541e298dbd20e6bd09d The fix for the ClassCastException: https://git.eclipse.org/c/jdt/eclipse.jdt.debug.git/commit/?id=e045ffff028c71d51f97538113250975ebb89c66 Probably we need an if-else-if-else with JDI object value, else JDI primitive value, else nothing. But we must understand first how to construct a case like this. Maybe a local class definition that uses outer scope primitive type variables.
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.
