From: Sandra Loosemore <sandra@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [patch] fix remote host test failures in gdb.base/dup-sect.exp
Date: Thu, 04 Apr 2013 11:09:00 -0000 [thread overview]
Message-ID: <515CF061.1090508@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
The two tests at the end of gdb.base/dup-sect.exp have been failing in
remote-host i686-mingw32 testing because the file containing the
stripped debug information isn't being made available on the remote
host. I stole this fix from another test case that also uses
gdb_gnu_strip_debug to produce separate debug info.
OK to commit?
-Sandra
2013-04-03 Sandra Loosemore <sandra@codesourcery.com>
gdb/testsuite/
* gdb.base/dup-sect.exp: Copy debug info file to remote host.
[-- Attachment #2: dup-sect.patch --]
[-- Type: text/x-patch, Size: 745 bytes --]
Index: gdb/testsuite/gdb.base/dup-sect.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/dup-sect.exp,v
retrieving revision 1.5
diff -u -p -r1.5 dup-sect.exp
--- gdb/testsuite/gdb.base/dup-sect.exp 1 Jan 2013 06:33:25 -0000 1.5
+++ gdb/testsuite/gdb.base/dup-sect.exp 4 Apr 2013 03:07:40 -0000
@@ -74,6 +74,13 @@ if {$result != 0} {
}
pass $test
+# gdb_gnu_strip_debug puts the debug info in $binfile.debug. Make sure that
+# file is available on the remote host.
+set debugfile $binfile.debug
+if { [is_remote host] } {
+ set debugfile [remote_download host $debugfile]
+}
+
clean_restart $executable
gdb_test "p/d *(const char *) &var1" " = 1" "var1 after strip"
next reply other threads:[~2013-04-04 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 11:09 Sandra Loosemore [this message]
2013-04-04 17:00 ` Pedro Alves
2013-04-04 19:27 ` Sandra Loosemore
2013-04-05 7:21 ` Pedro Alves
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=515CF061.1090508@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=gdb-patches@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: link
Be 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