Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [obv] testsuite: gdb.cp/ref-types.exp: Excessive newline
Date: Wed, 02 Jun 2010 21:40:00 -0000	[thread overview]
Message-ID: <20100602214003.GA31569@host0.dyn.jankratochvil.net> (raw)

Hi,

there has been now checked-in random
	FAIL: gdb.cp/ref-types.exp: print value of rL

Checked-in the fix.


Thanks,
Jan


http://sourceware.org/ml/gdb-cvs/2010-06/msg00019.html

--- src/gdb/testsuite/ChangeLog	2010/06/02 20:03:15	1.2302
+++ src/gdb/testsuite/ChangeLog	2010/06/02 21:38:32	1.2303
@@ -1,3 +1,7 @@
+2010-06-02  Jan Kratochvil  <jan.kratochvil@redhat.com>
+
+	* gdb.cp/ref-types.exp (print value of UI): Remove excessive newline.
+
 2010-06-02  Michael Snyder  <msnyder@msnyder-server.eng.vmware.com>
 
 	* gdb.cp/class2.exp: Use gdb_test_no_output.
--- src/gdb/testsuite/gdb.cp/ref-types.exp	2010/06/01 18:18:35	1.15
+++ src/gdb/testsuite/gdb.cp/ref-types.exp	2010/06/02 21:38:32	1.16
@@ -254,7 +254,7 @@
 gdb_test "print rI" ".\[0-9\]* = \\(int &\\) @$hex: 102" \
         pass "print value of rI"
 
-gdb_test "print rUI\n" \
+gdb_test "print rUI" \
     ".\[0-9\]* = \\(unsigned int &\\) @$hex: 1002" \
         pass "print value of UI"
 


             reply	other threads:[~2010-06-02 21:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 21:40 Jan Kratochvil [this message]
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
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=20100602214003.GA31569@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.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