Hi, I think this is causing the lldb-cmake test to hang on Green Dragon. The build revision numbers don't exactly match up for reasons I don't quite understand, but when I locally run check-lldb this is the test that spins for ages, and reverting this change doesn't move the timeout elsewhere.
I think the root of the issue is that macOS's debugserver has a very different command-line interface from lldb-server, it bails and that causes the pipe read to hang. But there seem to be other issues when I try to run it manually too: tim@timn ~/llvm/llvm-project/lldb $ /opt/local/Library/Frameworks/Python.framework/Versions/3.6/Resources/Python.app/Contents/MacOS/Python /Users/tim/llvm/llvm-project/lldb/lit/tools/lldb-mi/target/inputs/target-select-so-path.py /Users/tim/llvm/build.lldb/bin/debugserver /Users/tim/llvm/build.lldb/bin/lldb-mi --synchronous /Users/tim/llvm/build.lldb/tools/lldb/lit/tools/lldb-mi/target/Output/target-select-so-path.test.tmp /Users/tim/llvm/llvm-project/lldb/lit/tools/lldb-mi/target/target-select-so-path.test FileCheck: Unknown command line argument '--synchronous'. Try: 'FileCheck -help' FileCheck: Did you mean '-version'? FileCheck: Not enough positional command line arguments specified! Must specify at least 1 positional argument: See: FileCheck -help debugserver: unrecognized option `--pipe' debugserver-@(#)PROGRAM:LLDB PROJECT:lldb-360.99.0 for x86_64. error: failed to launch process /Users/tim/llvm/build.lldb/bin/debugserver: No such file or directory (localhost:0) Exiting. (It doesn't exit, it hangs). Could you take a look? Cheers. Tim. _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
