Re: [RFC 0/2, gdbserver] Set linux target in async mode in default

[Pedro Alves <palves@redhat.com>]

On 09/18/2012 10:47 AM, Yao Qi wrote:
> Hi,
> When writing the V2 of 'A general notification in GDB RSP' patch
> series, I find async mode isn't turned on unless non-stop mode is
> turned on.  After I generalize 'async notification' and support both
> non-stop and all-stop, it is required to turn async on even in all-stop
> mode.  Async can be regarded as an infrastructure in linux target to
> serve for other functionalities, such as 'notification' and
> 'non-stop'.  This is what patch 1/2 tries to do.  Regression tested on
> x86_64-linux with boardfile ntaive-gdbserver and
> native-extended-gdbserver.
> 
> After patch 1/2 is applied, target_async is not used in common code,
> so patch 2/2 is to remove macro target_async and field 'async' in
> struct 'target_ops' as a cleanup.

Please explain better why this is necessary (probably with an example).
What exactly doesn't work if you don't do this change?  It sounds as though
this could make gdbserver push notifications down to GDB in all-stop
mode even when it isn't waiting for server replies?

-- 
Pedro Alves