Re: MI: frozen variable objects

Nick Roberts
2006-11-16T23:07:41Z

> > 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.

> Do you think this would do any good?

AFAICS the first change (Variable objects laziness) is optimisation of existing
behaviour. It looks sound to me overall but, with the many conditionals, could
easily introduce new bugs. I see no urgency and as I don't have a deep
understanding of all the details the only way I can really check it is to
use it within Emacs. Maybe the second change is safer as it is a new feature,
although it could still clearly impact on existing behaviour.

> As far as I know, you and Vlad
> are the only people who ever test GDB/MI from CVS with frontends.

Alan Magloire has also said to me that he will check changes to MI with
Eclipse but I don't know how that relates to your interest in Eclipse.

> I'm not particularly inclined to wait, since none of this will show up
> unless your target / IDE specifically try to use it, but I'm sure I
> could be persuaded.

If existing behaviour is broken it _should_ show up. A six month release cycle
doesn't seem long to wait especially coming from Emacs whose last mainline
release was Oct 2001 (GDB 5.3 was current when I started!). Maybe there is
another agenda with Emacs, I don't know, but presumably it will be released one
day and I would like it to work with current GDB when it is.

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