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 18:05:00 -0000 [thread overview]
Message-ID: <4DC043B9.6040403@redhat.com> (raw)
In-Reply-To: <201105031850.46894.pedro@codesourcery.com>
On 05/03/2011 07:50 PM, Pedro Alves wrote:
> You're assuming I already knew the fail was of "interactive prompt"
> kind. :-) I didn't, but I now ran the test and see the failure. Seeing
> this also helps review:
>
> FAIL: gdb.base/pr10179.exp: delete breakpoints (got interactive prompt)
> FAIL: gdb.base/pr10179.exp: rbreak pr10179-a.c:foo.*
> FAIL: gdb.base/pr10179.exp: rbreak pr10179-a.c : .* (got interactive prompt)
>
> Knowing all this, your original patch was indeed trivial.
Yeah, I should have shown this before. Next time, I will.
> Okay, thanks, this is even better.
Applied: http://sourceware.org/ml/gdb-cvs/2011-05/msg00019.html
Thank you.
Marek
prev parent reply other threads:[~2011-05-03 18:05 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
2011-05-03 17:50 ` Pedro Alves
2011-05-03 18:05 ` Marek Polacek [this message]
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=4DC043B9.6040403@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