From: Pedro Alves <palves@redhat.com>
To: Tom de Vries <tdevries@suse.de>,
gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: [pushed] gdb.gdb/selftest.exp, Use multi_line to build gdb's expected startup output (Re: [PATCH, testsuite] Update gdb startup text in selftest.exp)
Date: Thu, 14 Jun 2018 11:51:00 -0000 [thread overview]
Message-ID: <1123408d-fbcd-70f5-af44-2064f8ab91b9@redhat.com> (raw)
In-Reply-To: <79521339-876f-f14a-c427-79f2e79f994a@redhat.com>
On 06/13/2018 12:49 PM, Pedro Alves wrote:
> That test could be made a lot more readable with use of multi_line.
I've pushed this in.
From 11ae5818f76e0af4dcf7ee069e0756ccf6901ebe Mon Sep 17 00:00:00 2001
From: Pedro Alves <palves@redhat.com>
Date: Thu, 14 Jun 2018 12:25:41 +0100
Subject: [PATCH] gdb.gdb/selftest.exp, Use multi_line to build gdb's expected
startup output
This regex had to be touched at least twice these past few days. Use
multi_line to make it more readable.
Note this also tightens the regex a little bit in some spots.
gdb/testsuite/ChangeLog:
2018-06-14 Pedro Alves <palves@redhat.com>
* gdb.gdb/selftest.exp (test_with_self): Use multi_line to build
gdb's expected startup output.
---
gdb/testsuite/ChangeLog | 5 +++++
gdb/testsuite/gdb.gdb/selftest.exp | 11 ++++++++++-
2 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index fd6b8fcbf2f..aa568a8343f 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,8 @@
+2018-06-14 Pedro Alves <palves@redhat.com>
+
+ * gdb.gdb/selftest.exp (test_with_self): Use multi_line to build
+ gdb's expected startup output.
+
2018-06-14 Pedro Alves <palves@redhat.com>
* lib/selftest-support.exp (selftest_setup): Remove inlined
diff --git a/gdb/testsuite/gdb.gdb/selftest.exp b/gdb/testsuite/gdb.gdb/selftest.exp
index 314bddb8bf2..3b200a28c53 100644
--- a/gdb/testsuite/gdb.gdb/selftest.exp
+++ b/gdb/testsuite/gdb.gdb/selftest.exp
@@ -63,10 +63,19 @@ proc test_with_self { } {
# Wait a bit while the inferior gdb gets to its prompt.
sleep 1
} else {
+ set banner [multi_line \
+ "GNU gdb \[0-9\.\]*\[^\r\n\]*" \
+ "Copyright \\(C\\) \[0-9\]* Free Software Foundation, Inc\." \
+ "License GPLv3\\+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>" \
+ "This is free software: you are free to change and redistribute it\." \
+ "There is NO WARRANTY, to the extent permitted by law\." \
+ "Type \"show copying\" and \"show warranty\" for details\." \
+ "This GDB was configured as .*" \
+ "$gdb_prompt $"]
set test "xgdb is at prompt"
gdb_test_multiple "continue" $test {
-i "$inferior_spawn_id"
- -re "GNU gdb \[0-9\.\]*.*Copyright \\(C\\) \[0-9\]* Free Software Foundation, Inc.*License GPLv3\\+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.*This is free software: you are free to change and redistribute it.*There is NO WARRANTY, to the extent permitted by law\..*Type \"show copying\".*and \"show warranty\" for details.*This GDB was configured as .*$gdb_prompt $" {
+ -re "$banner" {
pass $test
}
}
--
2.14.3
prev parent reply other threads:[~2018-06-14 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 14:10 [PATCH, testsuite] Update gdb startup text in selftest.exp Tom de Vries
2018-06-13 11:50 ` Pedro Alves
2018-06-14 11:51 ` Pedro Alves [this message]
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=1123408d-fbcd-70f5-af44-2064f8ab91b9@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
--cc=tom@tromey.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