clayborg added a comment. > The motivation for this test was the observation that an asanified LLDB would > often exhibit seemingly random test failures that could be traced back to > debugserver packets getting out of sync. With this path applied I can no > longer reproduce the one particular failure mode that I was investigating.
I hate that GDB remote packets can get out of sync. We should really think about adding sequence IDs to the GDB remote packets and responses and teach our GDB communication code to correctly deal with these. So many weird problems happen when things get out of sync. Repository: rLLDB LLDB CHANGES SINCE LAST ACTION https://reviews.llvm.org/D60340/new/ https://reviews.llvm.org/D60340 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
