jimingham wrote: Actually, the test will be a little harder than that because the deadlock comes between the main lldb work and async work done by the status line. So my test, which just runs lldb in Python, wouldn't have shown that error.
I wonder if it would be possible to have a version of the status line that is always running, just discarding its output if there's no Terminal to write it to. As it stands, the test suite isn't doing exercising the interaction between lldb and the status line filling thread nearly as much as our users now are... https://github.com/llvm/llvm-project/pull/148774 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
