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

228 lines
5.6 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, 1997 Free Software Foundation, Inc.
* 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
#
# 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_target_monitor
# Set gdb to target the monitor
#
proc gdb_target_monitor { exec_file } {
global gdb_prompt
* 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
global exit_status
global timeout
* 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
verbose "Timeout is now $timeout seconds" 2
if [target_info exists gdb_protocol] {
set targetname "[target_info gdb_protocol]"
} else {
perror "No protocol specified for [target_info name].";
return -1;
}
if [target_info exists baud] {
gdb_test "set remotebaud [target_info baud]" "" ""
}
if [target_info exists gdb_serial] {
set serialport "[target_info gdb_serial]";
} elseif [target_info exists netport] {
set serialport "[target_info netport]"
} else {
set serialport "[target_info serial]"
}
for {set j 1} {$j <= 2} {incr j} {
if [gdb_file_cmd $exec_file] { return -1; }
for {set i 1} {$i <= 3} {incr i} {
send_gdb "target $targetname $serialport\n"
gdb_expect {
-re "A program is being debugged already.*ill it.*y or n. $" {
send_gdb "y\n";
exp_continue;
}
-re "Couldn't establish connection to remote.*$gdb_prompt" {
verbose "Connection failed";
}
-re "Remote MIPS debugging.*$gdb_prompt" {
verbose "Set target to $targetname";
return 0;
}
-re "Remote debugging using $serialport.*$gdb_prompt" {
verbose "Set target to $targetname";
return 0;
}
-re "Remote target $targetname connected to.*$gdb_prompt" {
verbose "Set target to $targetname";
return 0;
* 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 "Ending remote.*$gdb_prompt" { }
-re "Connection refused.*$gdb_prompt" {
* 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
verbose "Connection refused by remote target. Pausing, and trying again."
sleep 30
continue
}
timeout {
send_gdb "";
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
}
}
}
gdb_target_exec;
if { $j == 1 && ![reboot_target] } {
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, port is $serialport.";
return -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
}
proc gdb_target_exec { } {
gdb_test "target exec" "No exec file now." "" ".*Kill it.*y or n.*" "y"
}
* 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 gdb_prompt
global timeout
* 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
if { $arg == "" } {
send_gdb "info files\n";
gdb_expect {
-re "Symbols from \"(\[^\"\]+)\"" {
set arg $expect_out(1,string);
exp_continue;
}
-re "Local exec file:\[\r\n\]+\[ \t\]*`(\[^'\]+)'," {
set arg $expect_out(1,string);
exp_continue;
}
-re "$gdb_prompt $" { }
}
}
for { set j 1; } { $j <= 2 } {incr j; } {
if [target_info exists gdb,use_standard_load] {
gdb_target_exec;
remote_push_conn host;
set state [remote_ld target $arg];
remote_close target;
remote_pop_conn host;
if { $state == "pass" } {
if [gdb_target_monitor $arg] { return -1; }
gdb_test "list main" ".*" ""
verbose "Loaded $arg into $GDB\n";
return 0;
}
} else {
if [gdb_target_monitor $arg] { return -1 }
if [is_remote host] {
# FIXME: Multiple downloads. bleah.
set farg [remote_download host $arg];
} else {
set farg $arg;
}
if { $arg != "" && [target_info exists gdb_sect_offset] } {
set textoff [target_info gdb_sect_offset];
send_gdb "sect .text $textoff\n";
gdb_expect {
-re "(0x\[0-9a-z]+) - 0x\[0-9a-z\]+ is \\.data" {
set dataoff $expect_out(1,string);
exp_continue;
}
-re "(0x\[0-9a-z\]+) - 0x\[0-9a-z\]+ is \\.bss" {
set bssoff $expect_out(1,string);
exp_continue;
}
-re "$gdb_prompt" { }
}
set dataoff [format 0x%x [expr $dataoff + $textoff]];
set bssoff [format 0x%x [expr $bssoff + $textoff]];
send_gdb "sect .data $dataoff\n";
gdb_expect {
-re "$gdb_prompt" { }
}
send_gdb "sect .bss $bssoff\n";
gdb_expect {
-re "$gdb_prompt" { }
}
}
verbose "Loading $farg"
if [target_info exists gdb_load_offset] {
set command "load $farg [target_info gdb_load_offset]\n";
} else {
set command "load $farg\n";
}
send_gdb $command;
set timeout 1200
verbose "Timeout is now $timeout seconds" 2
gdb_expect {
-re "\[Ff\]ailed.*$gdb_prompt $" {
verbose "load failed";
}
-re "Timeout reading from remote.*$gdb_prompt" {
}
-re "$gdb_prompt $" {
verbose "Loaded $farg into $GDB\n"
return 0;
}
timeout {
if { $verbose > 1 } {
perror "Timed out trying to load $farg."
}
}
* 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
}
}
# Make sure we don't have an open connection to the target.
gdb_target_exec;
if { $j == 1 } {
if { ![reboot_target] } {
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 load file into GDB.";
return -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
}
proc gdb_start { } {
global gdb_prompt;
* 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
if [board_info target exists gdb_prompt] {
set gdb_prompt [board_info target gdb_prompt];
}
catch default_gdb_start;
}