Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Martin Galvan <martin.galvan@tallertechnologies.com>
To: gdb-patches@sourceware.org
Subject: [PING][PATCH] testsuite: Escape a loose '[' character inside a regexp.
Date: Sat, 20 Jun 2015 04:47:00 -0000	[thread overview]
Message-ID: <1434775646-2625-1-git-send-email-martin.galvan@tallertechnologies.com> (raw)

Seems like an obvious fix to me, but I wanted to check just in case.
Ok to commit?

---
 gdb/testsuite/ChangeLog   | 4 ++++
 gdb/testsuite/lib/gdb.exp | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index e01f883..95338b3 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2015-06-13  Martin Galvan  <martin.galvan@tallertechnologies.com>
+
+	* lib/gdb.exp (test_class_help): Escape a loose '['.
+
 2015-06-12  Antoine Tremblay  <antoine.tremblay@ericsson.com>
 
 	PR breakpoints/16465
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 41797e7..2be9ba4 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -4674,7 +4674,7 @@ proc test_class_help { command_class expected_initial_lines args } {
     set l_stock_body {
         "List of commands\:.*\[\r\n\]+"
         "Type \"help\" followed by command name for full documentation\.\[\r\n\]+"
-        "Type \"apropos word\" to search for commands related to \"word\"\.[\r\n\]+"
+        "Type \"apropos word\" to search for commands related to \"word\"\.\[\r\n\]+"
         "Command name abbreviations are allowed if unambiguous\." 
     }
     set l_entire_body [concat $expected_initial_lines $l_stock_body]
-- 
2.4.3


             reply	other threads:[~2015-06-20  4:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-20  4:47 Martin Galvan [this message]
2015-06-22  9:10 ` Yao Qi
2015-06-23 15:50   ` Doug Evans
2015-06-23 15:57     ` Martin Galvan
2015-06-23 16:09     ` Doug Evans
2015-06-23 17:05       ` Andreas Schwab
2015-06-23 17:13         ` Doug Evans
2015-06-23 16:28     ` Yao Qi
2015-06-23 16:43       ` Doug Evans

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=1434775646-2625-1-git-send-email-martin.galvan@tallertechnologies.com \
    --to=martin.galvan@tallertechnologies.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