mgorny added a comment. I don't think we can reliably check whether additional threads aren't run then.
I have another idea that could work better if we could assume that the scheduler runs threads of the same process somehow evenly — or well, I suppose it'd be better in any case. Rather than stopping the process from LLDB, I could add a counter that issues SIGSTOP from inside the process after doing N (say, 5) prints. I suppose that should give it enough time for all threads to output something. Just need to figure out a simple synchronization method to ensure that SIGSTOP is emitted only once. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D126983/new/ https://reviews.llvm.org/D126983 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
