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

[Marc Khouzam <marc dot khouzam at ericsson dot com>]

> -----Original Message-----
> From: gdb-patches-owner@sourceware.org 
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Yao Qi
> Sent: Tuesday, September 18, 2012 5:48 AM
> To: gdb-patches@sourceware.org
> Subject: [RFC 0/2, gdbserver] Set linux target in async mode 
> in default
> 
> 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.

To clarify, after this patch we can still use "-gdb-set target-async off"
to turn off async mode right?

Eclipse currently uses non-async mode for all-stop and some code
is based on that assumption (e.g., interrupting the target)
so we need to keep non-async available.

Thanks

Marc

> 
> 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.
> 
>