[gdb/testsuite] Fix clean_restart <absolute filename> in gdb.linespec

Fix clean_restart <absolute filename> in the test-cases in gdb.linespec.

Tested on x86_64-linux.

diff --git a/gdb/testsuite/gdb.linespec/explicit.exp b/gdb/testsuite/gdb.linespec/explicit.exp
index 12eaa51f5ef9cd016109186e145eb7eddf040002..b859b4443ee887c68b413313e31d46e608e2844e 100644 (file)
--- a/gdb/testsuite/gdb.linespec/explicit.exp
+++ b/gdb/testsuite/gdb.linespec/explicit.exp
@@ -608,7 +608,7 @@ namespace eval $testfile {
     }
 
     # Test interaction of condition command and explicit linespec conditons.
-    clean_restart [standard_output_file $exefile]
+    clean_restart $exefile
 
     set tst "condition_command overrides explicit linespec condition"
     if {![runto_main]} {

diff --git a/gdb/testsuite/gdb.linespec/line-breakpoint-outside-function.exp b/gdb/testsuite/gdb.linespec/line-breakpoint-outside-function.exp
index 012be6bbd53eddfbba743741dfaa62449a933303..120ee6cae40450fc5ef51482f4ac0a32c2c6f51d 100644 (file)
--- a/gdb/testsuite/gdb.linespec/line-breakpoint-outside-function.exp
+++ b/gdb/testsuite/gdb.linespec/line-breakpoint-outside-function.exp
@@ -32,7 +32,7 @@ if {[build_executable "failed to prepare" ${testfile} ${srcfile} $opts]} {
 }
 
 proc do_test {} {
-    clean_restart $::binfile
+    clean_restart $::testfile
 
     # To make things easier, just so we don't have to deal with the question.
     gdb_test_no_output "set breakpoint pending on"