jingham added a comment. Note, a better way to do this would be to have some kind of "API/Runlock baton" that could get handed off from the thread that initiated the continue to the private state thread, then handed back when the process stops and returns control to the SB API that initiated the run. But I don't have time to design such a thing right now, and this was blocking writing tests for some work I am doing to handle the case where OS Plugins don't report all threads at each stop. So I'd prefer this more straightforward solution for now - especially since it's just a copy of the way we handled the same problem for the runlock.
Repository: rLLDB LLDB CHANGES SINCE LAST ACTION https://reviews.llvm.org/D68174/new/ https://reviews.llvm.org/D68174 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
