DavidSpickett wrote: Can you help me understand whether this is a wide issue that users will see, or there's something special about that test that makes the lldb-server prints a problem in that case.
Because it doesn't seem like an unusual test, except perhaps the strict ordering. I'd have expected a lot more tests to be broken by the issue you describe. So I wonder if we should be saying "no prints from lldb-server". And even if we did say that, if you use lldb-server on Windows and enable any log channel in it, do you also get this problem? Perhaps it only happens if you let lldb spawn the lldb-server for you, if you set it up separately it's in its own terminal so it's not a problem. (and if you want to see the logs from lldb-server, that's what you should be doing anyway) https://github.com/llvm/llvm-project/pull/205572 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
