Introduce the initial support for handling multiple ContinueDelegates
in GDBRemoteClientBase::SendContinuePacketAndWaitForResponse(). This
is the first step towards moving to a shared asynchronous thread serving
multiple ProcessGDBRemote instances.
The final goal is that every stop response will be passed through all
ContinueDelegates, and every delegate will decide whether it is
applicable to its process. The additional handled parameter is used
to indicate that the correct delegate has been found and no further
delegates need to be invoked.
The next step is going to involve decoupling the async thread from
ProcessGDBRemote itself, and moving all the logic responsible for
updating the process status into ContinueDelegate API.
Sponsored by: The FreeBSD Foundation
Why not just make this a regular return value?