Community
Participate
Working Groups
Build Identifier: CDT HEAD This feature requires the ability on gdb side to evaluate the full expression for the associated varobj. The gdb can't do that for varobjs that have a dynamic ancestor. Thus we should (ideally) disable it for such expressions. (Note that it still works for a dynamic varobj that doesn't have a dynamic ancestor). Background: The action is handled in org.eclipse.cdt.debug.internal.ui.actions.CastToTypeActionHandler, and I don't see a way to control its enabled state. Another approach could be ti check for CastedExpressionDMC in MIExpressions and add special handling, like no children, the values like "N/A (child of pretty-printed object)" as value, etc. Reproducible: Always