after the inferior gdb has started.
'cuz lynx may take a couple minutes to start the inferior gdb...
* gdb.base/a2-run.exp: Handle gdb echoing more than one cr-lf
after each command.
* gdb.base/funcargs.exp: Likewise.
* gdb.base/gdbvars.exp: Likewise.
* gdb.base/interrupt.exp: Likewise.
* gdb.base/list.exp: Likewise.
* gdb.base/watchpoint.exp: Likewise.
* gdb.c++/demangle.exp: Likewise.
* gdb.c++/inherit.exp: Likewise.
* gdb.chill/chexp.exp: Likewise.
* gdb.fortran/exprs.exp: Likewise.
Just in case we can't get a version of expect that sets the tty modes
right on lynx to avoid this problem.
config/rom68k.exp: New tcl glue for the appropriate monitors.
These all just end up calling monitor.exp.
* config/monitor.exp (gdb_target_monitor): Handle `Connection
refused' by retrying. Cleanup some timeout issues.
* (gdb_load): Reduce timeout. Cleanup some timeout issues.
* lib/gdb.exp (gdb_test gdb_test_exact): Upvar timeout so that
callers don't have to set/restore global timeout variable.
* The following set of changes centralizes management of the global
timeout variable. This way, it can be set in one target dependent
place instead of dozens of places scattered throughout the test suite.
If you need to lengthen a timeout, then you should either set timeout
in one of the config/{target}.exp files, or multiply it by a factor.
Setting it to an absolute value is always going to lose for some
targets.
* gdb.base/a1-selftest.exp (test_with_self): Only use local timeout.
* gdb.base/callfuncs.exp (do_function_calls): Don't set timeout.
* gdb.base/funcargs.exp: Don't set timeout.
* gdb.base/list.exp (test_forward_search): Only use local timeout.
* gdb.base/printcmds.exp (test_print_string_constants
test_print_array_constants): Don't set timeout.
* gdb.base/ptype.exp: Don't set timeout.
* gdb.base/recurse.exp: Don't set timeout.
* gdb.base/return.exp: Don't set timeout.
* gdb.base/watchpoint.exp: Don't set timeout.
* gdb.c++/classes.exp (do_tests): Don't set timeout.
* gdb.c++/virtfunc.exp (test_virtual_calls): Don't set timeout.
somewhere between `read' and `main.c'. I'm pretty sure the
pattern ".*#\[0-9\].*" was slowing down pattern matching a lot,
and it isn't particularly useful.
was a vestige of the manual TESTSTRATEGY, and the purpose of it
was to make sure that gdb can read a core file. But (a) the "read
the corefile" part didn't make it to a1-selftest.exp, we just
delete the corefile after creating it, and (b) we test reading
corefiles in corefile.exp anyway. Also, this test left around a
xgdb process on Solaris.
* gdb.base/corefile.exp: Also test backtrace.
when we'll be getting lots of output from gdb.
* gdb.base/a1-selftest.exp: Move code that was inside expect -re
"init_malloc" to after the expect statement. Run it if that
regexp is taken, but also for two others which happen if source
cannot be found.
