This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] gdb.python/py-evthreads.exp: fix racy test (PR testsuite/12649)
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: Marek Polacek <mpolacek at redhat dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Wed, 6 Jul 2011 10:26:16 -0700
- Subject: Re: [PATCH] gdb.python/py-evthreads.exp: fix racy test (PR testsuite/12649)
- References: <4E09E2C1.2020909@redhat.com> <20110628155107.GL20676@adacore.com> <4E0C4F28.4000703@redhat.com> <20110706171145.GB28535@host1.jankratochvil.net>
> It is a difference as it requires the end of the read buffer that way.
>
> If GDB outputs some
> (gdb) unexpected_result
>
> then (without any read1 hacks) -re "$gdb_prompt $" will FAIL/timeout as it
> should while -re "$gdb_prompt " could give a false PASS.
>
> (I do not think it requires a new commit, it is up to you.)
Let's fix it. If anything, we should be consistent. I might have
a minute later today, but I don't want to make the change without
running the testcase... So, I won't mind if someone gets to it before
I do.
--
Joel