From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/6] Fix several cases of racy output matching
Date: Thu, 09 Nov 2017 22:50:00 -0000 [thread overview]
Message-ID: <f66f4c9e-f2c8-347d-a710-4d2d2d7bef08@redhat.com> (raw)
In-Reply-To: <1509039747-15026-1-git-send-email-palves@redhat.com>
On 10/26/2017 06:42 PM, Pedro Alves wrote:
> After <https://sourceware.org/ml/gdb-patches/2017-10/msg00751.html>, I
> had the bright idea of running the whole testsuite with "make
> check-read1", and that exposed a number of problems.
>
> This fixes a good chunk of those. (There are more in at least gdb.mi/
> and gdb.python/.)
>
> Pedro Alves (6):
> Fix racy output matching in gdb.asm/asm-source.exp
> Fix racy output matching in gdb.base/completion.exp
> Fix racy output matching in gdb.base/memattr.exp
> Fix racy output matching in gdb.base/cpcompletion.exp
> Fix racy output matching in gdb.base/multi-attach.exp,
> gdb.server/ext-{attach, restart, ext-run}.exp
> Fix racy output matching in gdb.tui/tui-completion.exp
I've pushed these in now.
Thanks,
Pedro Alves
prev parent reply other threads:[~2017-11-09 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 17:42 Pedro Alves
2017-10-26 17:42 ` [PATCH 4/6] Fix racy output matching in gdb.base/cpcompletion.exp Pedro Alves
2017-10-26 17:42 ` [PATCH 1/6] Fix racy output matching in gdb.asm/asm-source.exp Pedro Alves
2017-10-26 17:42 ` [PATCH 6/6] Fix racy output matching in gdb.tui/tui-completion.exp Pedro Alves
2017-11-15 16:09 ` Simon Marchi
2017-11-15 16:16 ` Pedro Alves
2017-10-26 17:42 ` [PATCH 2/6] Fix racy output matching in gdb.base/completion.exp Pedro Alves
2017-10-26 17:42 ` [PATCH 5/6] Fix racy output matching in gdb.base/multi-attach.exp, gdb.server/ext-{attach, restart, ext-run}.exp Pedro Alves
2017-10-26 17:42 ` [PATCH 3/6] Fix racy output matching in gdb.base/memattr.exp Pedro Alves
2017-11-09 22:50 ` Pedro Alves [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=f66f4c9e-f2c8-347d-a710-4d2d2d7bef08@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).