> Could you please post a full patch, including changelog?  I'm finding
 > that when you update just bits of a patch in each message, it is
 > virtually impossible for me to find all of the current pieces.  I think
 > this patch will be fine, though.

Sure.  The code change is just one line (below).  The testsuite changes are
in the attachment.


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


2007-02-05  Nick Roberts  <nickrob@snap.net.nz>

	* mi/mi-cmd-var.c (mi_cmd_var_create): Add value field.


2007-02-05  Nick Roberts  <nickrob@snap.net.nz>

	* gdb.mi/mi-var-block.exp, gdb.mi/mi2-var-block.exp,
	* gdb.mi/mi-var-child.exp, gdb.mi/mi2-var-child.exp,
	* gdb.mi/mi-var-child-f.exp, gdb.mi/mi-var-cmd.exp,
	* gdb.mi/mi2-var-cmd.exp, gdb.mi/mi-var-display.exp,
	* gdb.mi/mi2-var-display.exp, gdb.mi/gdb701.exp,
        * gdb.mi/gdb792.exp, gdb.mi/gdb792.exp,
	* lib/mi-support.exp:
	Update tests to include value field in output of -var-create.


*** mi-cmd-var.c	10 Jan 2007 11:56:57 +1300	1.28
--- mi-cmd-var.c	18 Jan 2007 17:26:48 +1300	
*************** mi_cmd_var_create (char *command, char *
*** 125,131 ****
    if (var == NULL)
      error (_("mi_cmd_var_create: unable to create variable object"));
  
!   print_varobj (var, PRINT_NO_VALUES, 0 /* don't print expression */);
  
    do_cleanups (old_cleanups);
    return MI_CMD_DONE;
--- 125,131 ----
    if (var == NULL)
      error (_("mi_cmd_var_create: unable to create variable object"));
  
!   print_varobj (var, PRINT_ALL_VALUES, 0 /* don't print expression */);
  
    do_cleanups (old_cleanups);
    return MI_CMD_DONE;