clayborg wrote: I think the patch seems good as it is without needing to differentiate really. What are we gaining by hiding something that is trying to report progress that can take some time? Wouldn't we want to know this in a sys diagnose situation? If a python command runs for a long time, I would want to be able to report what the script was doing via progress and see the output without having to go and modify lldb-dap to handle some new progress event type. We already have the issue with python commands where if we don't have the ability to write to stdout and have it show up, then we need to register an immediate file to the SBCommandReturnObject which is kind of hacky, and that only works if the debugger's STDOUT hasn't been redirected to /dev/null.
https://github.com/llvm/llvm-project/pull/119052 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
