* gdb.base/corefile.exp: Allow "Core was generated by ..."
messages to not include the full program name that caused
the core dump since some systems (such as solaris) apparently
truncate this path to about 80 characters.
When generating a core file first try increasing the core file
size limit to unlimited since some systems may default it to
zero, and it is harmless to try it. Move the test for failing
to generate a core file to where it will actually get executed.
* gdb.c++/templates.exp (test_ptype_of_templates): Accept
new gdb result from g++ debug info improvements and make old
pattern obsolescent. Also account for size_t differences
(may be int or long).
* gdb.base/a1-selftest.exp (test_with_self): Check for case where
initialization before function call is placed in the delay slot
and thus appears to be skipped over by commands such as "next".
"bt in signals.exp".
* gdb.base/a1-selftest.exp: Add alpha-dec-osf2 setup_xfail for
"step over execarg initialization" and
"step over corearg initialization".
* gdb.base/ptype.c (main): Declare malloc as a "char *" for systems
with sizeof(pointer) > sizeof(int). Avoid "void *" or include files.
i*86-*-linux* xfails for "backtrace through signal handler".
* gdb.base/corefile.exp: Add i*86-*-sysv4* xfail for
"print func2::coremaker_local".
* gdb.base/break.exp: Add i*86-*-sysv4*, sparc-sun-sunos4,
xfail for
"delete all breakpoints when none".
"backtrace through signal handler" to "i*86-*-sysv4*".
* gdb.base/signals.exp: Add xfail for "'next' behaved as
continue" case. Add "known SVR4 bug" to fail message.
Add "i*86-*-bsdi2.0" xfail for "handle all print".
Add "i*86-*-bsdi2.0" xfail for "backtrace in signals_tests_1".
* gdb.base/ptype.exp: Add "i*86-*-sysv4*" xfail for
"whatis unnamed typedef'd enum..." and "ptype t_char_array".
* gdb.base/langs.exp: Add "i*86-*-sysv4*" xfail for
"up to foo in langs.exp", "show language at foo in
langs.exp", "up to cppsub_ in langs.exp", "show
language at cppsub_ in langs.exp", "up to fsub in
langs.exp", and "show language at fsub in langs.exp".
* gdb.base/corefile.exp: Add "i*86-*-sysv4*" to xfail for
"bactrace in corefile.exp".
* gdb.base/callfuncs.exp: Change xfail to "i*86-*-*" for
"call inferior function with struct - returns float" and
"call inferior function with struct - returns double".
"call function when asleep" and "send end of file".
* gdb.base/corefile.exp: Add "i*86-*-linuxaout" to xfail list
for "backtrace in corefile.exp".
* gdb.base/a1-selftest.exp: Add "i*86-*-linux*" to xfail list
for "backtrace through signal handler".
* gdb.base/corefile.exp: Make sure we actually generate a core file
before trying the core tests. Some systems allow the user to suppress
generation of core files and default to that (linux for example).
* gdb.base/signals.exp: Change xfail for "next" acting like "continue"
from "i*86-*-linux" to "i*86-*-linuxaout". Works with ELF beta.
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.
