Re: Avoid timeouts in call-sc.exp

[Michael Chastain <mec dot gnu at mindspring dot com>]

Good logs!

Both of the logs show similar de-synchronization.

The problem starts here in ppc32.gdb.log:

  p/c L
  $2 = 90 'Z'
  (gdb) PASS: gdb.base/call-sc.exp: zed L for return; return call-sc-tc
  return foo
  Make fun return now? (y or n) y
  reading register fpscr (#70): Input/output error.
  (gdb) FAIL: gdb.base/call-sc.exp: return foo; return call-sc-tc
  p/c L
  $3 = 90 'Z'
  (gdb) FAIL: gdb.base/call-sc.exp: value foo returned; return call-sc-tc
  advance fun
  main () at ./gdb.base/call-sc.c:78
  78            L = fun ();
  (gdb) FAIL: gdb.base/call-sc.exp: advance to fun for finish; return call-sc-tc
  p/c L

I presume the I/O error on fpscr is a bug in gdb.
After the bug happens, variable 'L' is not set to its new value.
And then "advance" starts from some de-synchronized place.

ppc64.gdb.log has the same problem.