Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>,
	Eli Zaretskii <eliz@gnu.org>
Subject: Re: Regression for gdb.mi/mi-reverse.exp  [Re: [committed]: [PATCH 2/2] MI notification on record started and stopped]
Date: Fri, 21 Sep 2012 07:26:00 -0000	[thread overview]
Message-ID: <505C1668.5060309@codesourcery.com> (raw)
In-Reply-To: <20120921065816.GA3748@host2.jankratochvil.net>

On 09/21/2012 02:58 PM, Jan Kratochvil wrote:
>   PASS: gdb.mi/mi-reverse.exp: mi runto main
>   Expecting: ^(-interpreter-exec console record[^M
> -]+)?(\^done[^M
> +]+)?(=record-started,id="1"^M
> +\^done[^M
>   ]+[(]gdb[)] ^M
>   [ ]*)
>   -interpreter-exec console record^M
> +=record-started,thread-group="i1"^M

After changed the output in "=record-started" notification, I forgot to
update the expected output here, and it causes the regression.

Committed.

-- 
Yao

gdb/testsuite:

2012-09-21  Yao Qi  <yao@codesourcery.com>

	* gdb.mi/mi-reverse.exp: Fix the typo in expected output of
	"=record-started" notification.
---
 gdb/testsuite/gdb.mi/mi-reverse.exp |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/gdb/testsuite/gdb.mi/mi-reverse.exp b/gdb/testsuite/gdb.mi/mi-reverse.exp
index 974a095..06a0943 100644
--- a/gdb/testsuite/gdb.mi/mi-reverse.exp
+++ b/gdb/testsuite/gdb.mi/mi-reverse.exp
@@ -51,7 +51,7 @@ mi_run_to_main
 if [supports_process_record] {
     # Activate process record/replay
     if [mi_gdb_test "-interpreter-exec console record" \
-	    "=record-started,id=\"1\"\r\n\\^done" \
+	    "=record-started,thread-group=\"i1\"\r\n\\^done" \
 	    "Turn on process record"] {
 	warning "Fail to activate process record/replay, tests in this group will not be performed.\n";
 	return -1
-- 
1.7.7.6



  reply	other threads:[~2012-09-21  7:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12  7:16 [PATCH 0/2] Two MI notifications on TSV and process record Yao Qi
2012-09-12  7:16 ` [PATCH 2/2] MI notification on record started and stopped Yao Qi
2012-09-12 17:52   ` Eli Zaretskii
2012-09-13  8:57     ` Yao Qi
2012-09-13 17:33       ` Eli Zaretskii
2012-09-14  2:54         ` Yao Qi
2012-09-14  9:49           ` Eli Zaretskii
2012-09-14 11:45             ` Yao Qi
2012-09-14 12:09               ` Pedro Alves
2012-09-14 13:14                 ` Yao Qi
2012-09-14 14:13                   ` Pedro Alves
2012-09-21  1:47                     ` [committed]: " Yao Qi
2012-09-21  6:58                       ` Regression for gdb.mi/mi-reverse.exp [Re: [committed]: [PATCH 2/2] MI notification on record started and stopped] Jan Kratochvil
2012-09-21  7:26                         ` Yao Qi [this message]
2012-09-14 13:30               ` [PATCH 2/2] MI notification on record started and stopped Eli Zaretskii
2012-09-12 18:07   ` Tom Tromey
2012-09-12 19:04     ` Pedro Alves
2012-09-12 19:01   ` Pedro Alves
2012-09-12  7:16 ` [PATCH 1/2] MI notification on tsv created and deleted Yao Qi
2012-09-12 17:48   ` Eli Zaretskii
2012-09-18 12:19     ` [committed]: " Yao Qi
2012-09-13 20:17   ` Tom Tromey

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=505C1668.5060309@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=palves@redhat.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