Re: linux native async mode support

[Nick Roberts <nickrob at snap dot net dot nz>]

 > > Daniel talks about async mode being the default but I don't really
 > > understand this.  In order for Gdb to be able to accept input while the
 > > inferior is running and possibly accepting it's own input, seems to require
 > > separate terminals.  This isn't a problem for a front end but, in general,
 > > will be when Gdb is run from the command line.
 > 
 > This is a confusion of terms.  The async mode he was refering to, is
 > the event loop code path, in which we (ideally) never block in
 > wait_for_inferior.

Maybe it will be useful in non-stop mode but it seems to me that there will
always be a problem when the inferior tries to read from/write to the terminal.
In any case, async mode is immediately useful for a frontend so, to begin with,
it might be a good idea to turn it on by default just for MI.

-- 
Nick                                           http://www.inet.net.nz/~nickrob