From: Yao Qi <yao@codesourcery.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Pedro Alves <palves@redhat.com>, Eli Zaretskii <eliz@gnu.org>,
Hui Zhu <hui_zhu@mentor.com>,
gdb-patches ml <gdb-patches@sourceware.org>,
Marc Khouzam <marc.khouzam@ericsson.com>
Subject: Re: [PATCH] add -s option to make -break-insert support dprintf
Date: Mon, 22 Apr 2013 01:25:00 -0000 [thread overview]
Message-ID: <51724F9A.4070204@codesourcery.com> (raw)
In-Reply-To: <CANFwon0MPymGC12ZUYYy_C+yNCBSOMFK4uK9DdivCAjdcu5N9w@mail.gmail.com>
On 04/15/2013 10:57 PM, Hui Zhu wrote:
> + mi_run_cmd
> + set msg "mi 1st dprintf"
> + gdb_expect {
> + -re ".*At foo entry.*arg=1234, g=1234.*" {
Hui,
Probably we need to remove the trailing ".*" above. Then, the rest of
the output will be matched ...
> + pass $msg
> + }
> + -re ".*$mi_gdb_prompt$" {
> + fail $msg
> + }
> + timeout {
> + fail $msg
> + }
> + }
> + mi_expect_stop ".*" ".*" ".*" ".*" ".*" "" "$msg stop"
... here.
> +
> + set msg "mi 2nd dprintf"
> + mi_send_resuming_command "exec-continue" "$msg continue"
> + gdb_expect {
> + -re ".*At foo entry.*arg=1235, g=2222.*" {
We need append "$mi_gdb_prompt$" to the end of the pattern above to eat
all the output, otherwise, these output will make troubles to the rest
of the tests.
> + pass $msg
> + }
> + -re ".*$mi_gdb_prompt$" {
> + fail $msg
> + }
> + timeout {
> + fail $msg
> + }
> + }
I can get some fails on my machine, similar to fails that Pedro pointed
out. With these change above, I don't see fails any more.
b.t.w,
+# To make sure set dprintf-style agent get right output.
+mi_gdb_test "pwd" ".*"
This line is odd to me, and looks it only papers over the problem
somewhere else.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-04-20 8:20 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 17:44 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 [this message]
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 ` [patch] Fix racy FAILs #2 " Jan Kratochvil
2013-05-24 15:37 ` [commit] " 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=51724F9A.4070204@codesourcery.com \
--to=yao@codesourcery.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 \
/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