Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	tromey@redhat.com, palves@redhat.com,        hui_zhu@mentor.com,
	gdb-patches@sourceware.org,        marc.khouzam@ericsson.com
Subject: [patch] Fix racy FAILs #2 due to "read1"  [Re: [PATCH] add -s option to make -break-insert support dprintf]
Date: Thu, 23 May 2013 14:03:00 -0000	[thread overview]
Message-ID: <20130523140332.GA11729@host2.jankratochvil.net> (raw)
In-Reply-To: <CANFwon0zgYPbBdj4U-x_OqVUtjg35WAmMp1Gmyy6b=i6Ne-9qg@mail.gmail.com>

On Tue, 21 May 2013 06:24:16 +0200, Hui Zhu wrote:
> Checked in http://sourceware.org/ml/gdb-cvs/2013-05/msg00193.html

I got another racy FAIL today:

FAIL: gdb.mi/mi-dprintf.exp: mi info dprintf second time

I found I forgot to run the "read1" reproducer with gdbserver yesterday, which
revealed more races.

I will check it in today.


Regards,
Jan


gdb/testsuite/
2013-05-23  Jan Kratochvil  <jan.kratochvil@redhat.com>

	PR testsuite/12649
	* gdb.mi/mi-dprintf.exp (mi_continue_dprintf) (mi 2nd dprintf): Replace
	$mi_gdb_prompt expectation by mi_expect_stop.
	(mi 1st dprintf, agent, mi 2nd dprintf, agent)
	(mi info dprintf second time): Replace them by mi_send_resuming_command
	and mi_expect_stop.

diff --git a/gdb/testsuite/gdb.mi/mi-dprintf.exp b/gdb/testsuite/gdb.mi/mi-dprintf.exp
index ea8b3a8..3509963 100644
--- a/gdb/testsuite/gdb.mi/mi-dprintf.exp
+++ b/gdb/testsuite/gdb.mi/mi-dprintf.exp
@@ -83,7 +83,7 @@ proc mi_continue_dprintf {args} {
 	set msg "mi 2nd dprintf"
 	mi_send_resuming_command "exec-continue" "$msg continue"
 	gdb_expect {
-            -re ".*At foo entry.*arg=1235, g=2222.*$mi_gdb_prompt$" {
+            -re ".*At foo entry.*arg=1235, g=2222" {
 		pass $msg
 	    }
 	    -re ".*$mi_gdb_prompt$" {
@@ -93,6 +93,7 @@ proc mi_continue_dprintf {args} {
 		fail $msg
             }
 	}
+	mi_expect_stop ".*" ".*" ".*" ".*" ".*" "" "$msg 2nd stop"
     }
 }
 
@@ -135,11 +136,28 @@ gdb_expect {
 if $target_can_dprintf {
     mi_run_cmd
 
-    mi_gdb_test "continue" ".*breakpoint-hit.*func=\"foo\".*" "mi 1st dprintf, agent"
+    mi_expect_stop ".*" ".*" ".*" ".*" ".*" "" "mi expect stop"
 
-    mi_gdb_test "continue" ".*breakpoint-hit.*func=\"foo\".*" "mi 2nd dprintf, agent"
+    mi_send_resuming_command "exec-continue" "mi 1st dprintf continue, agent"
+    mi_expect_stop ".*" "foo" ".*" ".*" ".*" "" "mi 1st dprintf, agent"
 
-    mi_gdb_test "6-break-info" ".*modified.*" "mi info dprintf second time"
+    mi_send_resuming_command "exec-continue" "mi 2nd dprintf continue, agent"
+
+    # The =breakpoint-modified text is a part of the "-exec-continue" output.
+    set msg "mi info dprintf second time"
+    gdb_expect {
+	-re "=breakpoint-modified," {
+	    pass $msg
+	}
+	-re ".*$mi_gdb_prompt$" {
+	    fail "$msg"
+	}
+	timeout {
+	    fail "$msg"
+	}
+    }
+
+    mi_expect_stop ".*" "foo" ".*" ".*" ".*" "" "mi 2nd dprintf, agent"
 }
 
 mi_gdb_test "set dprintf-style foobar" ".*error.*" "mi set dprintf style to an unrecognized type"


  parent reply	other threads:[~2013-05-23 14:03 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 17:44 [PATCH] add -s option to make -break-insert support dprintf Hui Zhu
2013-03-28 18:37 ` Eli Zaretskii
2013-03-29 16:12   ` Hui Zhu
2013-03-29 16:13     ` Eli Zaretskii
2013-04-09 23:31     ` Pedro Alves
2013-04-10 19:44       ` Marc Khouzam
2013-04-10 19:45         ` Pedro Alves
2013-04-11  6:15       ` Hui Zhu
2013-04-11 17:47         ` Pedro Alves
2013-04-12 14:56           ` Hui Zhu
2013-04-12 15:22             ` Pedro Alves
2013-04-15 18:59               ` Hui Zhu
2013-04-15 19:41                 ` Pedro Alves
2013-04-16  9:31                   ` Hui Zhu
2013-04-22  1:25                 ` Yao Qi
2013-04-12 16:03             ` Eli Zaretskii
2013-04-13 14:16         ` Tom Tromey
2013-04-15 18:04           ` Hui Zhu
2013-04-15 19:36             ` Pedro Alves
2013-04-16  9:31               ` Hui Zhu
2013-04-22  0:18                 ` Tom Tromey
2013-04-22  9:07                   ` Hui Zhu
2013-04-25  6:51                     ` Tom Tromey
2013-05-03  5:43                       ` Hui Zhu
2013-05-07 20:50                         ` Tom Tromey
2013-05-10 10:57                           ` Hui Zhu
2013-05-10 15:24                             ` Tom Tromey
2013-05-11  2:38                               ` Hui Zhu
2013-05-11  7:29                                 ` Eli Zaretskii
2013-05-13  3:39                                   ` Hui Zhu
2013-05-13 15:55                                     ` Eli Zaretskii
2013-05-14  4:56                                       ` Hui Zhu
2013-05-20  7:31                                         ` Hui Zhu
2013-05-20 15:44                                           ` Eli Zaretskii
2013-05-21  4:25                                             ` Hui Zhu
2013-05-21  8:10                                               ` [patch] Fix racy FAILs due to "read1" [Re: [PATCH] add -s option to make -break-insert support dprintf] Jan Kratochvil
2013-05-21  9:30                                                 ` Hui Zhu
2013-05-21 15:01                                                   ` [commit] " Jan Kratochvil
2013-05-22  1:05                                                     ` Hui Zhu
2013-05-23 14:03                                               ` Jan Kratochvil [this message]
2013-05-24 15:37                                                 ` [commit] [patch] Fix racy FAILs #2 " Jan Kratochvil
2013-05-27 11:02                                                   ` Hui Zhu
2013-05-13 16:23                                 ` [PATCH] add -s option to make -break-insert support dprintf 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=20130523140332.GA11729@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.com \
    --cc=marc.khouzam@ericsson.com \
    --cc=palves@redhat.com \
    --cc=teawater@gmail.com \
    --cc=tromey@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