From: ppluzhnikov@google.com (Paul Pluzhnikov)
To: gdb-patches@sourceware.org
Cc: ppluzhnikov@google.com
Subject: [patch] Fix for gdb.base/args.exp when ~/.gdbinit has "set confirm off"
Date: Fri, 08 Aug 2008 17:16:00 -0000 [thread overview]
Message-ID: <20080808171555.5293C3A67D1@localhost> (raw)
Greetings,
gdb.base/args.exp has been failing for me (and it takes a looong
time to fail), because I have "set confirm off" in ~/.gdbinit.
Attached patch fixes that.
Committed as obvious.
--
Paul Pluzhnikov
2008-08-08 Paul Pluzhnikov <ppluzhnikov@google.com>
* gdb.base/args.exp: Prevent ~/.gdbinit from affecting test.
Index: gdb.base/args.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/args.exp,v
retrieving revision 1.14
diff -u -p -u -r1.14 args.exp
--- gdb.base/args.exp 6 Aug 2008 12:52:06 -0000 1.14
+++ gdb.base/args.exp 8 Aug 2008 17:07:42 -0000
@@ -71,7 +71,7 @@ proc args_test { name arglist } {
# Test that the --args are processed correctly.
#
set old_gdbflags $GDBFLAGS
-set GDBFLAGS "--args $binfile 1 3"
+set GDBFLAGS "-nx --args $binfile 1 3"
args_test basic {{1} {3}}
#
@@ -79,21 +79,21 @@ args_test basic {{1} {3}}
# The syntax needed is a little peculiar; DejaGNU treats the arguments as a
# list and expands them itself, since no shell redirection is involved.
#
-set GDBFLAGS "--args $binfile 1 {} 3"
+set GDBFLAGS "-nx --args $binfile 1 {} 3"
args_test "one empty" {{1} {} {3}}
#
# try with 2 empty args
#
-set GDBFLAGS "--args $binfile 1 {} {} 3"
+set GDBFLAGS "-nx --args $binfile 1 {} {} 3"
args_test "two empty" {{1} {} {} 3}
# Try with arguments containing literal single quotes.
-set GDBFLAGS "--args $binfile 1 '' 3"
+set GDBFLAGS "-nx --args $binfile 1 '' 3"
args_test "one empty (with single quotes)" {{1} {''} {3}}
-set GDBFLAGS "--args $binfile 1 '' '' 3"
+set GDBFLAGS "-nx --args $binfile 1 '' '' 3"
args_test "two empty (with single quotes)" {{1} {''} {''} {3}}
set GDBFLAGS $old_gdbflags
reply other threads:[~2008-08-08 17:16 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=20080808171555.5293C3A67D1@localhost \
--to=ppluzhnikov@google.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