From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] testsuite: Error on trailing newlines
Date: Mon, 28 Jun 2010 19:51:00 -0000 [thread overview]
Message-ID: <20100628195027.GA19297@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20100602230235.GH3019@adacore.com>
On Thu, 03 Jun 2010 01:02:35 +0200, Joel Brobecker wrote:
> > * lib/gdb.exp (gdb_test_multiple): Error on trailing newlines.
>
> This part is OK as far as I am concerned, but let's hold off on it
> for a couple of days, to see if others have any comment about it.
After 25 days going to check it in a day (or upon approval).
Changed the message text.
Rechecked no regressions on {x86_64,x86_64-m32,i686}-fedora13-linux-gnu.
Thanks,
Jan
gdb/testsuite/
2010-06-28 Jan Kratochvil <jan.kratochvil@redhat.com>
Joel Brobecker <brobecker@adacore.com>
* lib/gdb.exp (gdb_test_multiple): Error on trailing newlines.
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -573,6 +573,10 @@ proc gdb_test_multiple { command message user_code } {
set message $command
}
+ if [string match "*\[\r\n\]" $command] {
+ error "Invalid trailing newline in \"$message\" test"
+ }
+
# TCL/EXPECT WART ALERT
# Expect does something very strange when it receives a single braced
# argument. It splits it along word separators and performs substitutions.
next prev parent reply other threads:[~2010-06-28 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 21:40 [obv] testsuite: gdb.cp/ref-types.exp: Excessive newline Jan Kratochvil
2010-06-02 21:44 ` Joel Brobecker
2010-06-02 22:31 ` [patch] testsuite: Error on trailing newlines [Re: [obv] testsuite: gdb.cp/ref-types.exp: Excessive newline] Jan Kratochvil
2010-06-02 23:02 ` Joel Brobecker
2010-06-04 14:31 ` [patch] testsuite: Error on trailing newlines Jan Kratochvil
2010-06-28 19:51 ` Jan Kratochvil [this message]
2010-06-28 19:55 ` Joel Brobecker
2010-06-28 20:10 ` Jan Kratochvil
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=20100628195027.GA19297@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.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