Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Cc: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Subject: [PATCH] gdb.base/jit.exp: Add testcase name to log message
Date: Mon, 26 Sep 2011 05:52:00 -0000	[thread overview]
Message-ID: <1317015658-20878-1-git-send-email-emachado@linux.vnet.ibm.com> (raw)

Hi,

this minor patch just adds the testcase name to the log message, following the
common pattern from the others testcases. Ok to commit?

--
Edjunior

2011-09-26  Edjunior Machado  <emachado@linux.vnet.ibm.com>

	gdb/testsuite/
	* gdb.base/jit.exp: Add testcase name to log message

---
 gdb/testsuite/gdb.base/jit.exp |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gdb/testsuite/gdb.base/jit.exp b/gdb/testsuite/gdb.base/jit.exp
index a6a8cc0..6c4c424 100644
--- a/gdb/testsuite/gdb.base/jit.exp
+++ b/gdb/testsuite/gdb.base/jit.exp
@@ -59,7 +59,7 @@ proc one_jit_test {count match_str} {
     global verbose testfile solib_binfile_target solib_binfile_test_msg pf_prefix
 
     set old_pf_prefix $pf_prefix
-    set pf_prefix "one_jit_test-$count"
+    lappend pf_prefix "one_jit_test-$count:"
 
     clean_restart $testfile
 
@@ -97,7 +97,7 @@ proc one_jit_test {count match_str} {
     gdb_continue_to_breakpoint "break here 2"
     # All jit librares must have been unregistered
     gdb_test "info function jit_function" \
-	"All functions matching regular expression \"jit_function\":" \
+	"All functions matching regular expression \"jit_function\":" 
     set pf_prefix $old_pf_prefix
 }
 
-- 
1.6.0.2


             reply	other threads:[~2011-09-26  5:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26  5:52 Edjunior Barbosa Machado [this message]
2011-10-03 19:28 ` Tom Tromey
2011-10-03 20:21   ` Edjunior Barbosa Machado

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=1317015658-20878-1-git-send-email-emachado@linux.vnet.ibm.com \
    --to=emachado@linux.vnet.ibm.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