From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [commit, 6.0] Fix fileio test cleanup
Date: Sun, 27 Jul 2003 21:18:00 -0000 [thread overview]
Message-ID: <3F24418B.7080702@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 219 bytes --]
(suprised no one noticed)
I didn't quite get the switch from system->remote_exec right in the file
I/O tests. This fixes the problem - remote_exec wasn't doing shell
expansion.
committed to 6.0 and mainline,
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1185 bytes --]
2003-07-27 Andrew Cagney <cagney@redhat.com>
* gdb.base/fileio.exp: Use SH when running commands using
remote_exec.
Index: testsuite/gdb.base/fileio.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/fileio.exp,v
retrieving revision 1.3
diff -u -r1.3 fileio.exp
--- testsuite/gdb.base/fileio.exp 14 Jun 2003 16:51:42 -0000 1.3
+++ testsuite/gdb.base/fileio.exp 27 Jul 2003 20:44:49 -0000
@@ -52,8 +52,8 @@
return -1;
}
-remote_exec build "test -r dir2.fileio.test && chmod -f +w dir2.fileio.test"
-remote_exec build "rm -rf *.fileio.test"
+remote_exec build {sh -xc test\ -r\ dir2.fileio.test\ &&\ chmod\ -f\ +w\ dir2.fileio.test}
+remote_exec build {sh -xc rm\ -rf\ *.fileio.test}
set oldtimeout $timeout
set timeout [expr "$timeout + 60"]
@@ -269,9 +269,8 @@
send_gdb "quit\n"
send_gdb "y\n"
-remote_exec build "test -r dir2.fileio.test && chmod -f +w dir2.fileio.test"
-remote_exec build "rm -rf *.fileio.test"
+remote_exec build {sh -xc test\ -r\ dir2.fileio.test\ &&\ chmod\ -f\ +w\ dir2.fileio.test}
+remote_exec build {sh -xc rm\ -rf\ *.fileio.test}
set timeout $oldtimeout
return 0
-
next reply other threads:[~2003-07-27 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 21:18 Andrew Cagney [this message]
2003-07-27 21:26 ` Daniel Jacobowitz
2003-07-27 21:48 Michael Elizabeth Chastain
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=3F24418B.7080702@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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