DavidSpickett added a comment. I'm running `lldb/test/API/tools/lldb-server/memory-tagging/TestGdbRemoteMemoryTagging.py`.
If the details matter any... In qemu: $ ./build-cross/bin/lldb-server platform --server --listen 0.0.0.0:54321 On the host: $ ./bin/lldb-dotest --platform-name remote-linux --platform-url connect://192.168.53.89:54321 --platform-working-dir /tmp/test_lldb -p TestGdbRemoteMemoryTagging.py --arch aarch64 I have qemu setup so that any port lldb-server picks should be accessible from the host and the VM is just running the usual background linux stuff plus lldb-server. Not a lot to use up ports. Can you remind me what forward/reverse mean here? I guess that forward is us telling the remote the port to use, which might already be taken on the remote itself. Then reverse is the remote launching the lldb-server on a port it chooses, then telling us what it chose. The latter should be fine for my setup. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D117559/new/ https://reviews.llvm.org/D117559 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
