From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Marek Polacek <mpolacek@redhat.com>
Subject: Re: [PATCH] gdb.base/pr10179.exp: fix racy tests (PR testsuite/12649)
Date: Mon, 02 May 2011 19:24:00 -0000 [thread overview]
Message-ID: <201105022024.01156.pedro@codesourcery.com> (raw)
In-Reply-To: <4DBEE73B.3040202@redhat.com>
On Monday 02 May 2011 18:17:47, Marek Polacek wrote:
> This one is quite trivial.
Probably. But, it most probably only became trivial/obvious to you
after looking at the gdb.log around the FAIL, and noticing, "ahh,
the race is because FOO, and BAR". If you don't explain those FOOs
and BARs on your patch submission, whoever reviews the patch needs
to do about the same analysis work you've done.
Please, can you try again, with some explanation of _why_ is
it needed to ...
> It was needed to write the whole
> question instead of using the `.*' at the end. I have also
> added the message input.
... do these? For instance, break.exp doesn't appear to
need to match the whole question.
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'm not objecting or approving in any way, and it's really
probably trivial. Just trying to point out that if you make it
easier to okay your patches, you'll get okay's much quicker. :-)
> Ok?
>
> 2011-05-02 Marek Polacek <mpolacek@redhat.com>
>
> * gdb.base/pr10179.exp: Fix racy tests by completing
> the question properly. Also provide the message input.
>
>
> Index: gdb/testsuite/gdb.base/pr10179.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/pr10179.exp,v
> retrieving revision 1.2
> diff -u -r1.2 pr10179.exp
> --- gdb/testsuite/gdb.base/pr10179.exp 1 Jan 2011 15:33:42 -0000 1.2
> +++ gdb/testsuite/gdb.base/pr10179.exp 2 May 2011 17:09:34 -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"
> +gdb_test "delete breakpoints" "" "delete breakpoints" "Delete all breakpoints\\? \\(y or n\\) " "y"
>
> gdb_test "rbreak pr10179-a.c:foo.*" "Breakpoint \[0-9\]+\[^\\n\]*\\nint foo.*"
>
> -gdb_test "delete breakpoints" ".*" "" "Delete all breakpoints.*" "y"
> +gdb_test "delete breakpoints" "" "delete breakpoints" "Delete all breakpoints\\? \\(y or n\\) " "y"
>
> 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\]*.*"
>
--
Pedro Alves
next prev parent reply other threads:[~2011-05-02 19:24 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 [this message]
2011-05-03 16:53 ` Marek Polacek
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=201105022024.01156.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=mpolacek@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