to "alpha-*-osf2*" and add comment.
* gdb.base/a1-selftest.exp (test_with_self): Remove "alpha-dec-osf2*"
setup_xfail for "step over execarg initialization" and
"step over corearg initialization".
* gdb.base/callfuncs.exp (do_function_calls): Restore setup_xfail
for "hppa*-*-*", "sparc-*-*", "mips*-*-*", and "alpha-dec-osf2*".
* gdb.base/corefile.exp: Add "alpha-dec-osf2*" setup_xfail when not
gcc compiled for "print coremaker_bss", "print coremaker_ro",
"print func2::coremaker_local", and "backtrace in corefile.exp".
* gdb.base/signals.exp: Build and source signals.ci.
(test_handle_all_print): Add setup_xfail for "alpha-dec-osf2*".
Change "alpha-dec-osf2*" setup_xfail for "bt in signals.exp"
to be for gcc only.
* lib/gdb.exp: Move verbose statements outside conditionals.
from dejagnu's apparent default of 10 seconds, which gives random results
when running the tests over NFS on moderately loaded systems.
* lib/gdb.exp (gdb_run_cmd): Add "(timeout)" in timeout case.
the executable, not the .o to run the tests from.
Remove a useless step and avoid loading a .o into a target board
(loads into address zero which causes all kinds of problems).
if $noresults if nonzero.
* gdb.base/langs.exp: Likewise.
* gdb.base/watchpoint.exp: Likewise.
For proelf targets were we can't even tell if a process exits.
when trying to determine if a core file was generated.
If no core file was generate the first time, try again without
the ulimit -c to work around braindamaged shells.
Gets corefile.exp running again on the PA.
which sed script to run. Expect failure for v_comb test
on PA targets too.
Should get weird-stabs tests running on supported targets again.
I'd also expect most (if not all) stabs targets to fail v_comb...
* 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".
conflicts with later tests using test_print_reject in ../lib/gdb.exp.
(passcount): Remove.
* tests2.exp (test_print_accept): Removed.
(test_write): Re-write to use gdb_test rather than test_print_accept.
* tests1.exp (test_print_accept_exact): Removed.
(tests_locations): Rewrite to use gdb_test and not above proc.
