1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
# Test Framework Driver for GDB using the extended gdb remote protocol
# Copyright 1995, 1997 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.
#
# For this to function correctly, you need to set a number of variables
# in your gdb/site.exp file
#
# set noargs 1 -- we can't pass arguments (yet)
# set noinferiorio 1 -- we can't get io to/from the inferior
# set targethost <host> -- name of the remote system (runs gdbserver)
# set debughost <host> -- name of the system running gdb
# set port <number> -- starting port number for communication
# set gdbserver <path> -- path (on the remote side) to find
# gdbserver
# set rsh <path> -- path (on debughost side) to rsh
# set rcp <path> -- path (on debughost side) to rcp
#
# You will need to be able to spawn processes from gdbhost to run on
# targethost via rsh (this is how we start gdbserver); similarly
# you need to be able to rcp files from gdbhost to targethost.
#
# We don't do much error checking, if something goes wrong, you'll probably
# just get a tcl error and everything will die. FIXME
#
# Load the basic gdb testing library
load_lib gdb.exp
load_lib monitor.exp
#
# gdb_load -- load a file into the debugger.
# return a -1 if anything goes wrong.
#
# Loading a file in the gdbsrever framework is a little strange in that
# we also create the inferior (which is stopped at the first instruction
# in the program when we get control).
#
proc gdb_load { arg } {
global verbose
global loadpath
global loadfile
global GDB
global gdb_prompt
global debughost
global port
# bump the port number to avoid conflicts with hung ports
set targethost [target_info gdb_server_host];
set debughost [target_info gdb_debug_host];
if [target_info exists gdb_server_prog] {
set gdbserver [target_info gdb_server_prog];
} else {
set gdbserver "gdbserver";
}
incr port
set serialport $targethost:$port
# Copy the file down to the remote host.
set file [remote_download host $arg];
# now start gdbserver on the remote side
remote_spawn host "$gdbserver $debughost:$port $file >& /dev/null < /dev/null"
# give it plenty of time to get going (lynx)
sleep 30
# tell gdb we are remote debugging
if [gdb_target_monitor $arg] {
return -1;
}
return 1
}
#
# gdb_start -- start GDB running.
#
proc gdb_start { } {
global gdb_prompt
# do the usual stuff
catch default_gdb_start
# FIXME: This shouldn't be necessary, but lots of PA tests fail
# without it.
send "set remotecache 0\n"
expect {
-re "set remotecache 0\[\r\n\]+.*$gdb_prompt $" {}
default { fail "gdb_start"}
}
}
|
