[Lldb-commits] [PATCH] D117559: [lldb] Remove remote testing ability from lldb**-server** tests

David Spickett via Phabricator via lldb-commits lldb-commits at lists.llvm.org
Wed Jan 19 03:08:29 PST 2022

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

On the host:

  $ ./bin/lldb-dotest --platform-name remote-linux --platform-url connect:// --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.

  rG LLVM Github Monorepo



More information about the lldb-commits mailing list