I've noticed these failures when testing against a local gdbserver.

 Using ../../../src/gdb/testsuite/config/gdbserver.exp as tool-and-target-specific interface file.
 Running ../../../src/gdb/testsuite/gdb.python/python-value.exp ...
 FAIL: gdb.python/python-value.exp: continue to breakpoint: break to inspect struct and union
 FAIL: gdb.python/python-value.exp: print s
 FAIL: gdb.python/python-value.exp: access element inside struct using 8-bit string name
 FAIL: gdb.python/python-value.exp: access element inside struct using unicode name
 FAIL: gdb.python/python-value.exp: print argv
 FAIL: gdb.python/python-value.exp: dereference value
 FAIL: gdb.python/python-value.exp: verify dereferenced value

The issue here is the usage of gdb_start_cmd, which is a nop against stubs.

The attached fixes it here for me, both gdbserver, and native linux.

The race mentioned in the test seems to be related to the fact that gdb_start_cmd
doesn't wait for "main" to be reached at all.  The attached patch should get
rid of the need to work around that.

Tromey, Bauermann, OK to apply this?

-- 
Pedro Alves