> On Aug 14, 2018, at 2:43 PM, Александр Поляков <polyakov....@gmail.com> wrote:
>
> Here is what I got from gdb-remote packet log:
>
> (gdb)
> lldb-mi < 1> send packet: +
> lldb-mi history[1] tid=0x784a < 1> send packet: +
> lldb-mi < 19> send packet: $QStartNoAckMode#b0
> lldb-mi < 1> read packet: +
> lldb-mi < 6> read packet: $OK#9a
> lldb-mi < 1> send packet: +
> lldb-mi < 41> send packet: $qSupported:xmlRegisters=i386,arm,mips#12
> lldb-mi < 124> read packet:
> $PacketSize=20000;QStartNoAckMode+;QThreadSuffixSupported+;QListThreadsInStopReply+;qEcho+;QPassSignals+;qXfer:auxv:read+#be
> lldb-mi < 26> send packet: $QThreadSuffixSupported#e4
> lldb-mi < 6> read packet: $OK#9a
> lldb-mi < 27> send packet: $QListThreadsInStopReply#21
> lldb-mi < 6> read packet: $OK#9a
> lldb-mi < 13> send packet: $qHostInfo#9b
> lldb-mi < 11> send packet: $qEcho:1#5b
>
> Could somebody help me with understanding of what is happening here?
>
Just to clarify: Is this from a session that failed with the symptoms you
described earlier?
I'm not familiar with the protocol, but the fact that there are send and read
log entries makes it sound like the communication itself is working.
-- adrian
_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
