This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [doc] improve MI varobj introduction
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: Vladimir Prus <vladimir at codesourcery dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Wed, 20 Dec 2006 11:24:55 +1300
- Subject: Re: [doc] improve MI varobj introduction
- References: <200612191103.55137.vladimir@codesourcery.com>
I think it's a good idea to add this.
> +For a leaf variable object it is possible to obtain its value as a
> +string, or set the value from a string. String value can be also
^^^^^^
-var-assign var1 8 <- not a string
^done,value="8"
> +obtained for a non-leaf variable object, but its generally a string
> +that only indicates the type of the object, and does not list its
> +content. Assignment to a non-leaf variable object is not allowed.
>
> +A frontend need not read the values of all variable objects each time
> +the program stops. Instead, MI provides update command that lists all
> +variable objects which values has changed since the last update
> +operation. This considerably reduces the amount of data that must
> +be transferred to the frontend.
and this:
> + and return the
> +list of variable object which values has changed as the result.
and return the
list of variable object whose values have changed.
However, I'm not sure that the replaced parts of the introduction are an
improvement, or that elaborating on the PRINT-VALUES option is a good idea.
Also expanding the introduction allows the removal of the summary of commands
which just duplicates what comes after.
--
Nick http://www.inet.net.nz/~nickrob