Re: MI: frozen variable objects

Nick Roberts
2006-11-16T21:53:19Z

> This patch introduces so called "frozen" variable objects -- variable objects
> that are not implicitly updated by the "-var-update *" command or by
> "-var-update" on parent variable objects.

This explains your previous patch (Variable objects laziness):

+ We do this for frozen varobjs as well, since this
+ function is only called when it's decided that we need
+ to fetch the new value of a frozen variable. */

I've not experienced a need for such functionality probably because my Emacs
mode is still unreleased and therefore has a very small user base. Since you
and Daniel J see that it is needed (through Eclipse?) it seems sensible to
install a patch like this (and the earlier one, which I do understand now -
perhaps the ChangeLog could say "Use install_new_value instead of
gdb_value_fetch_lazy"). However, I would just suggest that these changes are
made shortly after the release of GDB 6.6. That way there is time test them
with frontends that might be using GDB/MI while GDB is still in CVS.

--
Nick http://www.inet.net.nz/~nickrob