Re: linux native async mode support

[Pedro Alves <pedro at codesourcery dot com>]

A Tuesday 18 March 2008 00:05:36, Nick Roberts wrote:
>  > New patch attached.  No regressions in async mode other than
>  > the same defines.exp regressions, and no regressions when async
>  > mode is disabled.  --- tested on x86-64-unknown-linux-gnu.
>
> I've tested it (evidently on i686-linux-gnu) with
>
>   set GDBFLAGS "-ex \"maint set linux-async on\""
>
> in site.exp, ignoring commands.exp  and just got a few extra exceptions:
>
>   FAIL: gdb.mi/mi-var-child-f.exp: mi runto MAIN__ (timeout)
>   FAIL: gdb.mi/mi-var-child-f.exp: create local variable array
>
>   FAIL: gdb.mi/mi2-simplerun.exp: continue to end (1)
>
>   FAIL: gdb.threads/pthreads.exp: check backtrace from main thread
>

Strange, I don't get any of these.  Could you try to see what's
different from a non-async run?  The first failure may be gdb
losing an event, although I haven't seen those in a while now.

> Are you going to add any new tests?

It seems you are!

Actually, passing all the testsuite in async (with simulated syncronous
mode) is already a good test coverage.  I feel like I hit
every possible problem already while writting this :-)  You're
right in that we're going to need tests for the new functionaly, ...

> My original test file mi-async.exp (attached below) works with your patch
> when GDBFLAGS is toggled as above.  It would be be good to have a test for
> -exec-interrupt too.

Yep.

... but please let's not prevent the not having many tests from putting
this in so more people can try it.

-- 
Pedro Alves