dlav-sc wrote: > @dlav-sc do you still have an interest in this? If not, I will close this PR.
Hi @DavidSpickett, I believe I still need this patch for two reasons: 1. I don't like the hardcoded ports used in the `GdbRemoteTestCases` for remote debugging (check out the `get_next_port()` function in `lldb/packages/Python/lldbsuite/test/tools/lldb-server/gdbremote_testcase.py`). These ports might be unavailable or not properly forwarded, which can lead to failures. 2. In our `CI` it is possible to have a situation when parallel testing of different builds make certain ports unavailable and `qemu` is not able to forward those. To avoid this issue, we can try forwarding different ports and using them instead. However, in this case, `dotest.py` needs to know which ports are available. The option I've added does just that - it tells `dotest.py` about the ports it can use during testing. https://github.com/llvm/llvm-project/pull/112555 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
