Hi, If a remote stub does not send the stop reply with thread information, current code in ProcessGDBRemote::SetThreadStopInfo() will not process the stop reply as thread_sp will be null. The patch tries to handle this case by updating the thread list and choosing the first one. LLDB interaction with QEMU gets much better after this patch. Also tested with gdbserver and did not see any issue. Although this control path is not entered in the gdbserver case as it does supply thread information with stop reply packets. OK to apply?
Regards, Abid
S_Packet.patch
Description: S_Packet.patch
_______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
