The effect of:
...
untested "y.exp"
...
in a gdb.x/y.exp is:
...
UNTESTED: gdb.x/y.exp: y.exp
...
which is a bit pointless.
Replace these untested messages in gdb.mi/*.exp with the usual "failed to
compile".
Likewise for an:
...
untested $testname
...
where the variable is undefined.
Tested on x86_64-linux.
standard_testfile basics.c
if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
- untested mi-regs.exp
+ untested "failed to compile"
return -1
}
standard_testfile
if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
- untested "mi-async-run.exp"
+ untested "failed to compile"
return -1
}
if {[gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" \
executable {debug}] != "" } then {
- untested mi-frame-regs.exp
+ untested "failed to compile"
return -1
}
close $f
if { [gdb_compile "$srcfileabs" "${binfile}" executable {debug}] != "" } {
- untested $testname
+ untested "failed to compile"
return -1
}
if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" \
"${binfile}" executable {debug}] != "" } {
- untested mi-vla-basics.exp
+ untested "failed to compile"
return -1
}