Re: [RFA] gdb.base/callfuncs.exp: make all test names unique

[Michael Elizabeth Chastain <chastain@cygnus.com>]

Committed.

I have four more files in progress:

  arithmet.exp
  assign.exp
  ena-dis-br.exp
  logical.exp

These are much bigger changes.  These files use a lot of
send_gdb/gdb_expect calls that can be calls to gdb_test instead, which
makes the files a lot shorter.  Plus I vaguely recall that people prefer
gdb_test over send_gdb/gdb_expect because it standardizes all the error
and timeout handling.

I'm planning to put up the first one (arithmet.exp) for comments this
weekend.  Any guidance here would be appreciated.

If anyone else wants to join the fun, here are more files with duplicate
test names:

  gdb.base/maint.exp
  gdb.base/miscexprs.exp
  gdb.base/opaque.exp
  gdb.base/page.exp
  gdb.base/pointers.exp
  gdb.base/printcmds.exp
  gdb.base/radix.exp
  gdb.base/relational.exp
  gdb.base/restore.exp
  gdb.base/return2.exp
  gdb.base/scope.exp
  gdb.base/shlib-call.exp
  gdb.base/signals.exp
  gdb.c++/annota2.exp
  gdb.c++/anon-union.exp
  gdb.c++/demangle.exp
  gdb.c++/inherit.exp
  gdb.c++/ref-types.exp
  gdb.chill/chexp.exp
  gdb.fortran/types.exp
  gdb.threads/pthreads.exp
  gdb.trace/passcount.exp

Michael