[binutils-gdb] [gdb/testsuite] Fix gdb.dwarf2/imported-unit-bp-c.exp for remote host
Tom de Vries
vries@sourceware.org
Mon Mar 27 11:59:02 GMT 2023
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b54e6df085a3a3c0a86d9e19419d8b4cfa3e5055
commit b54e6df085a3a3c0a86d9e19419d8b4cfa3e5055
Author: Tom de Vries <tdevries@suse.de>
Date: Mon Mar 27 13:58:10 2023 +0200
[gdb/testsuite] Fix gdb.dwarf2/imported-unit-bp-c.exp for remote host
Fix test-case gdb.dwarf2/imported-unit-bp-c.exp on remote by removing a
downloaded source file.
Tested on x86_64-linux.
Diff:
---
gdb/testsuite/gdb.dwarf2/imported-unit-bp.exp.tcl | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/gdb/testsuite/gdb.dwarf2/imported-unit-bp.exp.tcl b/gdb/testsuite/gdb.dwarf2/imported-unit-bp.exp.tcl
index 6bef2bdb089..62dee7d7992 100644
--- a/gdb/testsuite/gdb.dwarf2/imported-unit-bp.exp.tcl
+++ b/gdb/testsuite/gdb.dwarf2/imported-unit-bp.exp.tcl
@@ -122,5 +122,10 @@ if { [prepare_for_testing "failed to prepare" ${testfile} \
gdb_reinitialize_dir /tmp
+# Compilation on remote host downloads the source files to remote host, but
+# doesn't clean them up, allowing gdb to find $srcfile, in contrast to
+# non-remote host.
+remote_file host delete $srcfile
+
# Using an absolute path is important to see the bug.
gdb_test "break /tmp/${srcfile}:19" "Breakpoint .* file $srcfile, line .*"
More information about the Gdb-cvs
mailing list