Greg Clayton wrote on 16/02/2017 17:17:41:
> We seem to have a race condition here. Any help figuring out what
> that might be would be great.
I think I've now identified the problem.
Normally in lldb-server when the child lldb-server process is launched
inside GDBRemoteCommunication::StartDe
Greg Clayton wrote on 16/02/2017 17:17:41:
> this is just the first packet we send after sending the "ack" down
> to the remote server. When we send the "ack", we don't need a
> response, then we send the "QStartNoAckMode" packet and actually
> wait for a response. If we don't get one, then w
Greg Clayton wrote on 16/02/2017 17:17:41:
> Sounds like a race condition we need to solve.
It seemed likely but I thought I'd confirm that before I investigated too
deeply just in case there was anything obvious I'd missed.
> This sounds like a very common VM issue. If you can elaborate on
> On Feb 16, 2017, at 5:58 AM, Howard Hellyer via lldb-dev
> wrote:
>
> Hi,
>
> I’ve been hitting issues connecting to lldb-server. I’ve been trying from Mac
> to Linux running in a Virtual Box VM on the same machine. Once I’ve created a
> target and issued the “run” command lldb immediatel
