Re: MI: frozen variable objects

[Frederic RISS <frederic.riss@st.com>]

On Thu, 2006-11-16 at 06:58 -0700, Greg Watson wrote:
> I don't really understand the motivation for putting this kind of  
> functionality into gdb. Any GUI that is more than just a front-end  
> for gdb will most likely have an internal data structure representing  
> the value of the variable, and can retain or manage access to the  
> value if required. It seems to me that adding functionality like this  
> to gdb just adds to bloat when it is really a GUI function anyway.

The interesting part seems to be the one that hasn't been submited yet
about GDB auto-freezing some values due to archtectural requirements.
The debugger has architectural knowledge and it shouldn't be necessary
to duplicate it in the GUI.
I agree with your general point though. Maybe the functionality
shouldn't be in the debugger, but the information should be available to
the GUI... through varobj properties maybe? Of course this means that
the GUIs have to known about and respect this information.

Fred.