labath added a comment. In D94888#2505698 <https://reviews.llvm.org/D94888#2505698>, @dblaikie wrote:
> Out of curiousity did you find a way to get lldb-test to print out the > stdout/stderr of the underlying lldb process to see what error messages it > was producing that demonstrated this failure? I was trying to figure out how > to do that, and it seems like a good thing to be able to do for this issue or > others down the way. There's no underlying "lldb process" as these tests use lldb as a library through its python api. That said, adding `-t` (trace) to the lldb-dotest invocation will make it print more information about what the test is doing, though I am not entirely sure how much would it help in this case Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D94888/new/ https://reviews.llvm.org/D94888 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
