When I've checked in the patch to implement per-thread varobjs, I've
implicitly assumed that MI output does not change in single-threaded
programs, so no testsuite update is necessary. However, that's not
necessary true, and with Pedro's recent patch, is not true on x86.

Updating the testsuite should be trivial, except that MI testsuite
is poorly designed:

- Just about every test uses regular expression that the output
much match
- The expression is too rigid, so a new field in the output
breaks it.

So, I've checked in the below patch that makes just about every
test for -var-create and -var-list-children use helper functions.
Along the way, it allows the thread-id field in the output of
those commands.

Testing on x86 with and without printing of thread id for varobjs
shows no issues.

- Volodya

2008-03-26  Vladimir Prus  <vladimir@codesourcery.com>

	* lib/mi-support.exp (mi_create_varobj_checked): New.
	(mi_list_varobj_children): Allow to check for a
	value.
	(mi_list_array_varobj_children): New.

	* gdb.mi/mi-var-child.exp: Use mi_create_varobj
	and mi_list_varobj_children, as opposed to hardcoding
	expected strings.
	* gdb.mi/gdb701.exp: Likewise.
	* gdb.mi/gdb792.exp: Likewise.
	* gdb.mi/mi-var-block.exp: Likewise.
	* gdb.mi/mi-var-cmd.exp: Likewise.
	* gdb.mi/mi-var-invalidate.exp: Likewise.
	* gdb.mi/mi2-var-block.exp: Likewise.
	* gdb.mi/mi2-var-child.exp: Likewise.
	* gdb.mi/mi2-var-cmd.exp: Likewise.
	* gdb.mi/mi2-var-display.exp: Likewise.