Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFC/TESTSUITE]  completion.exp
Date: Tue, 08 Apr 2003 23:24:00 -0000	[thread overview]
Message-ID: <16019.23357.144916.774165@localhost.redhat.com> (raw)


Another one (I am going through the some RedHat Linux gdb patches, in
case it wasn't obvious).  This one is fairly specific, I am not sure
if it would be Ok for inclusion in the general sources, but just in case.

Again this is for the '+' character in the directory name.

elena

        * gdb.base/completion.exp: When matching on the current directory,
        make sure that any '+' in the directory name gets escaped.


Index: completion.exp
===================================================================
RCS file: /cvs/uberbaum/gdb/testsuite/gdb.base/completion.exp,v
retrieving revision 1.14
diff -u -p -r1.14 completion.exp
--- completion.exp	4 Jan 2003 22:37:49 -0000	1.14
+++ completion.exp	8 Apr 2003 23:18:00 -0000
@@ -669,7 +669,12 @@ cd ${srcdir}
 set fullsrcdir [pwd]
 cd ${mydir}
 
-gdb_test "cd ${fullsrcdir}" "Working directory ${fullsrcdir}.*" "cd to \${srcdir}"
+# If the directory name contains a '+' we must escape it, adding a backslash.
+# If not, the test below will fail because it will interpret the '+' as a 
+# regext operator.
+regsub -all \\+  ${fullsrcdir} \\\+ dirstring
+
+gdb_test "cd ${fullsrcdir}" "Working directory ${dirstring}.*" "cd to \${srcdir}"
 send_gdb "file ./gdb.base/compl\t"
 sleep 1
 gdb_expect  {


             reply	other threads:[~2003-04-08 23:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 23:24 Elena Zannoni [this message]
2003-04-09 17:23 ` David Carlton
2003-04-09 20:14   ` Elena Zannoni
2003-04-09 20:35     ` David Carlton
2003-04-09 20:57     ` Daniel Jacobowitz
2003-04-10 13:38       ` Elena Zannoni

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=16019.23357.144916.774165@localhost.redhat.com \
    --to=ezannoni@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