1 # Copyright 1999, 2000, 2001, 2002, 2003, 2005, 2007, 2008, 2009, 2010, 2011
2 # Free Software Foundation, Inc.
4 # This program is free software; you can redistribute it and/or modify
5 # it under the terms of the GNU General Public License as published by
6 # the Free Software Foundation; either version 3 of the License, or
7 # (at your option) any later version.
9 # This program is distributed in the hope that it will be useful,
10 # but WITHOUT ANY WARRANTY; without even the implied warranty of
11 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
12 # GNU General Public License for more details.
14 # You should have received a copy of the GNU General Public License
15 # along with this program. If not, see <http://www.gnu.org/licenses/>.
18 # test basic Machine interface (MI) operations
20 # Verify that, using the MI, we can load a program and do
21 # other basic things that are used by all test files through mi_gdb_exit,
22 # mi_gdb_start, mi_delete_breakpoints, mi_gdb_reinitialize_dir and
23 # mi_gdb_load, so we can safely use those.
25 # The goal is not to test gdb functionality, which is done by other tests,
26 # but the command syntax and correct output response to MI operations.
29 load_lib mi-support.exp
33 if [mi_gdb_start separate-inferior-tty] {
38 set srcfile ${testfile}.c
39 set binfile ${objdir}/${subdir}/mi-basics
40 set escapedobjdir [string_to_regexp ${objdir}]
41 set envirodir [string_to_regexp ${objdir}/${subdir}]
43 if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug additional_flags=-DFAKEARGV}] != "" } {
44 untested mi-basics.exp
48 # In this file we want to test if the operations needed by the following
49 # procedures work, so it makes no sense using them here.
51 # mi_delete_breakpoints
52 # mi_gdb_reinitialize_dir $srcdir/$subdir
53 # mi_gdb_load ${binfile}
55 # Test if the MI interpreter has been configured
57 proc test_mi_interpreter_selection {} {
61 # All this test expects is to get the prompt back
62 # with no syntax error message
63 gdb_test_multiple "-gdb-version" "acceptance of MI operations" {
64 -re "GNU gdb .*\r\n$mi_gdb_prompt$" {
65 pass "acceptance of MI operations"
68 -re ".*\r\n$mi_gdb_prompt$" {
69 fail "acceptance of MI operations"
71 -re "Undefined command.*$gdb_prompt $" {
72 fail "acceptance of MI operations"
75 note "Skipping all other MI tests."
79 proc test_exec_and_symbol_mi_operatons {} {
83 # Load symbols and specify executable on a single operation
85 # -file-exec-and-symbols
87 # Can't use mi_gdb_test as if this doesn't work,
88 # we must give up on the whole test file
89 gdb_test_multiple "-file-exec-and-symbols ${binfile}" \
90 "-file-exec-and-symbols ${binfile}" {
91 -re "\[\r\n\]*\\\^done\r\n$mi_gdb_prompt$" {
92 pass "file-exec-and-symbols operation"
95 fail "file-exec-and-symbols operation (timeout)"
96 note "Skipping all other MI tests."
101 # The following is not used by mi-support.exp, but we test here so
102 # we get done with loading a program basics.
104 # Do it again, but now load symbols and specify executable with
105 # two separate operations
111 # FIXME: file-clear is not implemented yet.
112 # mi_gdb_test "-file-clear" \
114 # "file-clear operation"
116 mi_gdb_test "-file-exec-file ${binfile}" \
118 "file-exec-file operation"
120 mi_gdb_test "-file-symbol-file ${binfile}" \
122 "file-symbol-file operation"
124 # FIXME: if we cannot load we have to skip all other tests.
127 proc test_breakpoints_deletion {} {
131 # Clear all breakpoints and list to confirm
133 # -break-delete (all)
136 # The all parameter is actually no parameter.
137 mi_gdb_test "200-break-delete" \
139 "break-delete (all) operation"
141 mi_gdb_test "201-break-list" \
142 ".*\\\^done,BreakpointTable=\\\{.*,body=\\\[\\\]\\\}" \
143 "all breakpoints removed"
146 proc test_dir_specification {} {
152 # Add to the search directories, display, then reset back to default
154 # -environment-directory arg
155 # -environment-directory
156 # -environment-directory -r
158 mi_gdb_test "202-environment-directory ${objdir}/${subdir}" \
159 "202\\\^done,source-path=\"${envirodir}.\\\$cdir.\\\$cwd\"" \
160 "environment-directory arg operation"
162 mi_gdb_test "203-environment-directory" \
163 "203\\\^done,source-path=\"${envirodir}.\\\$cdir.\\\$cwd\"" \
164 "environment-directory empty-string operation"
166 mi_gdb_test "204-environment-directory -r" \
167 "204\\\^done,source-path=\"\\\$cdir.\\\$cwd\"" \
168 "environment-directory operation"
171 proc test_cwd_specification {} {
177 # Change the working directory, then print the current working directory
179 # -environment-cd ${objdir}
182 mi_gdb_test "205-environment-cd ${objdir}" \
184 "environment-cd arg operation"
186 # The canonical name of the working directory may differ on a
187 # remote host from that on the build system.
188 if ![is_remote host] {
189 mi_gdb_test "206-environment-pwd" \
190 "206\\\^done,cwd=\"${escapedobjdir}\"" \
191 "environment-pwd operation"
195 proc test_path_specification {} {
203 # Add to the path, display, then reset
206 # -environment-path dir1 dir2
207 # -environment-path -r dir
208 # -environment-path -r
210 gdb_test_multiple "-environment-path" "-environment-path" {
211 -re "\\\^done,path=\"\(.*\)\"\r\n$mi_gdb_prompt" {
212 set orig_path $expect_out(1,string);
215 perror "-environment-path (timeout)" ;
220 set orig_path [string_to_regexp ${orig_path}]
221 set pathdir [string_to_regexp ${objdir}/${subdir}]
223 mi_gdb_test "207-environment-path" \
224 "207\\\^done,path=\"$orig_path\"" \
225 "environment-path no-args operation"
227 mi_gdb_test "208-environment-path $objdir ${objdir}/${subdir}" \
228 "208\\\^done,path=\"$escapedobjdir.${envirodir}.$orig_path\"" \
229 "environment-path dir1 dir2 operation"
231 mi_gdb_test "209-environment-path -r $objdir" \
232 "209\\\^done,path=\"$escapedobjdir.$orig_path\"" \
233 "environment-path -r dir operation"
235 mi_gdb_test "210-environment-path -r" \
236 "210\\\^done,path=\"$orig_path\"" \
237 "environment-path -r operation"
241 proc test_setshow_inferior_tty {} {
243 global mi_inferior_tty_name
245 # Test that the commands,
248 # are setting/getting the same data in GDB.
250 mi_gdb_test "301-inferior-tty-show" \
251 "301\\\^done,inferior_tty_terminal=\"$mi_inferior_tty_name\"" \
252 "initial tty is mi_inferior_tty_name"
254 mi_gdb_test "302-inferior-tty-set /dev/pts/1" \
256 "set tty to /dev/pts/1"
258 mi_gdb_test "303-inferior-tty-show" \
259 "303\\\^done,inferior_tty_terminal=\"/dev/pts/1\"" \
260 "tty was set correctly"
262 mi_gdb_test "304-inferior-tty-set" \
264 "set tty to the empty string"
266 mi_gdb_test "305-inferior-tty-show" \
268 "make sure tty is empty"
270 mi_gdb_test "306-inferior-tty-set $mi_inferior_tty_name" \
272 "set tty to mi_inferior_tty_name (the way it was)"
274 mi_gdb_test "307-inferior-tty-show" \
275 "307\\\^done,inferior_tty_terminal=\"$mi_inferior_tty_name\"" \
276 "verify tty is correct"
279 if [test_mi_interpreter_selection] {
280 test_exec_and_symbol_mi_operatons
281 test_breakpoints_deletion
282 test_dir_specification
283 test_cwd_specification
284 test_path_specification
285 test_setshow_inferior_tty