public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb/testsuite] Fix gdb.dwarf2/imported-unit-bp-c.exp for remote host Date: Mon, 27 Mar 2023 11:59:02 +0000 (GMT) [thread overview] Message-ID: <20230327115902.2C8853858C83@sourceware.org> (raw) 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 .*"
reply other threads:[~2023-03-27 11:59 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230327115902.2C8853858C83@sourceware.org \ --to=vries@sourceware.org \ --cc=gdb-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).