[PATCH,testsuite] fix pending.exp failure with remote targets

[Nathan Froyd <froydnj@codesourcery.com>]

The patch below fixes a problem with pending.exp.  pending.exp uses a
bare 'run' to start execution of the test, which is not appropriate for
remote targets like gdbserver.  The patch fixes this by using
gdb_run_cmd to start execution of the test.

Tested with cross to powerpc-linux-gnu.  OK to commit?

-Nathan

	* gdb.base/pending.exp: Use gdb_run_cmd to start the program
	instead of a bare "run".

Index: gdb.base/pending.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/pending.exp,v
retrieving revision 1.16
diff -u -u -r1.16 pending.exp
--- gdb.base/pending.exp	3 Jan 2009 05:58:03 -0000	1.16
+++ gdb.base/pending.exp	13 Nov 2009 19:10:19 -0000
@@ -71,7 +71,10 @@
 gdb_load_shlibs $lib_sl
 
 set pendfunc1_loc [gdb_get_line_number "y = x + 4" ${libfile}.c]
-gdb_test "run" \
+
+gdb_run_cmd
+
+gdb_test "" \
 ".*Breakpoint.*pendfunc1.*at.*pendshr.c:$pendfunc1_loc.*y = x \\+ 4.*" \
 "run to resolved breakpoint 1 (without symbols)"