old-cross-binutils/gdb/testsuite/config/monitor.exp

125 lines
2.7 KiB
Text
Raw Normal View History

* config/cpu32bug.exp, config/est.exp, config/hppro.exp, 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.
1995-05-11 01:03:50 +00:00
# Test Framework Driver for GDB driving a ROM monitor (via monitor.c).
# Copyright 1995 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */
* config/cpu32bug.exp, config/est.exp, config/hppro.exp, 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.
1995-05-11 01:03:50 +00:00
load_lib gdb.exp
#
# gdb_version -- extract and print the version number of gdb
#
proc gdb_version {} {
default_gdb_version
}
#
# gdb_target_monitor
# Set gdb to target the monitor
#
proc gdb_target_monitor { } {
global prompt
global exit_status
global targetname
global serialport
global baud
global target_info
* config/cpu32bug.exp, config/est.exp, config/hppro.exp, 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.
1995-05-11 01:03:50 +00:00
set timeout 60
if {$baud != ""} then {
send "set remotebaud $baud\n"
}
if [info exists target_info(target,cflags)] {
set targetname "$target_info(target,target)"
}
if [info exists target_info(target,netport)] {
set serialport "$target_info(target,netport)"
}
for {set i 1} {$i <= 3} {incr i} {
* config/cpu32bug.exp, config/est.exp, config/hppro.exp, 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.
1995-05-11 01:03:50 +00:00
send "target $targetname $serialport\n"
expect {
-re "Remote target $targetname connected to.*$prompt $" {
verbose "Set target to $targetname"
return
* config/cpu32bug.exp, config/est.exp, config/hppro.exp, 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.
1995-05-11 01:03:50 +00:00
}
-re "Connection refused" {
verbose "Connection refused by remote target. Pausing, and trying again."
sleep 30
continue
}
timeout {
break
* config/cpu32bug.exp, config/est.exp, config/hppro.exp, 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.
1995-05-11 01:03:50 +00:00
}
}
}
perror "Couldn't set target for $targetname."
cleanup
exit $exit_status
* config/cpu32bug.exp, config/est.exp, config/hppro.exp, 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.
1995-05-11 01:03:50 +00:00
}
#
# gdb_load -- load a file into the debugger.
# return a -1 if anything goes wrong.
#
proc gdb_load { arg } {
global verbose
global loadpath
global loadfile
global GDB
global prompt
if [gdb_file_cmd $arg] then { return -1 }
gdb_target_monitor
verbose "Loading $arg"
send "load $arg\n"
* config/cpu32bug.exp, config/est.exp, config/hppro.exp, 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.
1995-05-11 01:03:50 +00:00
set timeout 600
expect {
-re ".*$prompt $" {
if { $verbose > 1 } {
* config/cpu32bug.exp, config/est.exp, config/hppro.exp, 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.
1995-05-11 01:03:50 +00:00
send_user "Loaded $arg into $GDB\n"
}
return 1
}
-re "$prompt $" {
if { $verbose > 1 } {
perror "GDB couldn't load."
* config/cpu32bug.exp, config/est.exp, config/hppro.exp, 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.
1995-05-11 01:03:50 +00:00
}
}
timeout {
if { $verbose > 1 } {
* config/cpu32bug.exp, config/est.exp, config/hppro.exp, 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.
1995-05-11 01:03:50 +00:00
perror "Timed out trying to load $arg."
}
}
}
}
#
# gdb_start -- start GDB running.
#
proc gdb_start { } {
default_gdb_start
}
#
# gdb_exit -- exit gdb
#
proc gdb_exit { } {
catch default_gdb_exit
}
gdb_start