From: Marek Polacek <mpolacek@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb.base/pr10179.exp: fix racy tests (PR testsuite/12649)
Date: Tue, 03 May 2011 16:53:00 -0000 [thread overview]
Message-ID: <4DC032F1.3030705@redhat.com> (raw)
In-Reply-To: <201105022024.01156.pedro@codesourcery.com>
On 05/02/2011 09:24 PM, Pedro Alves wrote:
> Please, can you try again, with some explanation of _why_ is
> it needed to ...
You are right, I'm sorry. Thus, here is another try.
> For instance, break.exp doesn't appear to
> need to match the whole question.
In break.exp, there are no `gdb_test "delete breakpoints"'.
> Not sure the original PR 10179 had something to do with
> deleting breakpoints, otherwise, there's a delete_breakpoints
> procedure tests can use to do this.
I think the best thing here is to make use of the `delete_breakpoints', since
pr10179.exp addresses to test the `rbreak', not deleting the breakpoints.
Replacing `gdb_test "delete breakpoints"' with delete_breakpoints also
cures the races. IIUC, the race was caused by this part:
"Delete all breakpoints.*" "y"
Thus, when using read1(), we match the question "Delete all breakpoints?
(y or n)" right after the "breakpoints" word. This will leave in the buffer
"? (y or n)". The "(y or n)" matches and causes the "interactive prompt" fail.
Here is a better patch. Tested with both read{,1}. OK now? Thanks,
2011-05-03 Marek Polacek <mpolacek@redhat.com>
* gdb.base/pr10179.exp: Get rid of races using `delete_breakpoints'
in place of `gdb_test "delete breakpoints"'. This eliminates two
testcases.
Index: pr10179.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/pr10179.exp,v
retrieving revision 1.2
diff -u -r1.2 pr10179.exp
--- pr10179.exp 1 Jan 2011 15:33:42 -0000 1.2
+++ pr10179.exp 3 May 2011 16:46:27 -0000
@@ -29,10 +29,10 @@
gdb_test "rbreak foo.*" "Breakpoint \[0-9\]+\[^\\n\]*\\nint foo\[12\]\[^\\n\]*\\nBreakpoint \[0-9\]+\[^\\n\]*\\nint foo\[12\].*"
-gdb_test "delete breakpoints" ".*" "" "Delete all breakpoints.*" "y"
+delete_breakpoints
gdb_test "rbreak pr10179-a.c:foo.*" "Breakpoint \[0-9\]+\[^\\n\]*\\nint foo.*"
-gdb_test "delete breakpoints" ".*" "" "Delete all breakpoints.*" "y"
+delete_breakpoints
gdb_test "rbreak pr10179-a.c : .*" "Breakpoint \[0-9\]+\[^\\n\]*\\nint bar1\[^\\n\]*\\nBreakpoint \[0-9\]+\[^\\n\]*\\nint foo1\[^\\n\]*\\nBreakpoint \[0-9\]+\[^\\n\]*\\nint main\[^\\n\]*.*"
next prev parent reply other threads:[~2011-05-03 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 17:18 Marek Polacek
2011-05-02 19:24 ` Pedro Alves
2011-05-03 16:53 ` Marek Polacek [this message]
2011-05-03 17:50 ` Pedro Alves
2011-05-03 18:05 ` Marek Polacek
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=4DC032F1.3030705@redhat.com \
--to=mpolacek@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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