Re: [RFC v5] fix regressions with target-async

[Pedro Alves <palves@redhat.com>]

This is OK, please push it in.

On 03/12/2014 04:42 PM, Tom Tromey wrote:

> While working on this I noticed that there don't seem to be any test
> cases that involve both target-async and record, so this patch changes
> break-precsave.exp to add some.  It also changes corefile.exp to add
> some target-async tests; these pass with current trunk and with this
> patch applied, but fail with the v1 patch.

I was looking at the async-by-default series, and pondering
this --- after the "target async by default" series,
"set target-async" is really an MI setting, so it'll be irrelevant
and really useless for these tests.  We'll have an alternative "maint
set target-async off/on", but I don't think we should use it to
force specific tests to run in sync mode -- rather my idea for it
was to it from a board file for the occasional comfortable testing and
emulation of !Linux targets.

So in the end, after the target-async series, I think we should go
through non-MI tests and remove all that do "set target-async on".

-- 
Pedro Alves