[testsuite,committed] Fix think-o in calls to gdb_compile
Commit Message
In cross-testing on an arm-none-linux-gnueabi toolchain, I found that
the test programs for gdb.base/nested-subp*.exp were being built without
the appropriate command-line options for an executable, which was
causing them to be un-runnable on the remote target. There's nothing
ARM-specific here -- the trouble turned out to be a think-o in the calls
to gdb_compile. It wants the literal token "executable" for the
argument corresponding to the "type" parameter, not the name of the
executable. I think this is a sufficiently obvious fix that I've gone
ahead and committed it.
-Sandra
@@ -26,7 +26,7 @@ set testcase "nested-subp1"
if { [gdb_compile "${srcdir}/${subdir}/${testcase}.c" \
[standard_output_file "${testcase}"] \
- "${testcase}" \
+ executable \
[list debug "additional_flags=-std=gnu99"]] != "" } {
return -1
}
@@ -26,7 +26,7 @@ set testcase "nested-subp2"
if { [gdb_compile "${srcdir}/${subdir}/${testcase}.c" \
[standard_output_file "${testcase}"] \
- "${testcase}" \
+ executable \
[list debug "additional_flags=-std=gnu99"]] != "" } {
return -1
}
@@ -26,7 +26,7 @@ set testcase "nested-subp3"
if { [gdb_compile "${srcdir}/${subdir}/${testcase}.c" \
[standard_output_file "${testcase}"] \
- "${testcase}" \
+ executable \
[list debug "additional_flags=-std=gnu99"]] != "" } {
return -1
}