Re: [PATCH]: MI -var-set-format

["Marc Khouzam" <marc.khouzam@ericsson.com>]

>> I thought the intentio was to commit Vladimir's patch too:
>>> 
>>>   http://sourceware.org/ml/gdb/2008-01/msg00116.html
>>> 
>>> perhaps using xstrdup instead of strdup.  I can then make appropriate
>>> changes to Emacs in the CVS repository prior to the release of 22.2.
>>
>> One thread at a time is all I can handle.  Have we concluded that the
>> above patch is better than always using natural format to check for
>> updates?
>
> I thought that was part of the thread.  Isn't Marc's patch for
> -var-evaluate-expression meant to meet his requirement for multiple formats?

In my case, I agreed that this solution is sufficient (and probably the least intrusive.)
But we do need Vladimir's patch.

Here is a small patch for the doc to explain this requirement.  Feel free to reword
of course.

Marc

### Eclipse Workspace Patch 1.0
#P gdb
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.459
diff -u -r1.459 gdb.texinfo
--- doc/gdb.texinfo     23 Jan 2008 11:26:29 -0000      1.459
+++ doc/gdb.texinfo     24 Jan 2008 21:32:51 -0000
@@ -20058,6 +20058,9 @@
 recommended to use the @samp{--all-values} option, to reduce the
 number of MI commands needed on each program stop.
 
+To know if a variable object or any of its children has changed value in any 
+format instead of only the current one, the variable object and all its children
+should be in the natural format before issuing the @code{-var-update} command.  
 
 @subsubheading Example