[Lldb-commits] [lldb] [lldb] Removed gdbserver ports map from lldb-server (PR #104238)

[David Spickett via lldb-commits]

DavidSpickett wrote:

I did some testing with my usual setup which is x86 Linux to AArch64 Linux running in a simulator.

```
<simulator>
$ ./lldb-server platform --server --listen 0.0.0.0:1234 --gdbserver-port 49140
<host>
$ ./bin/lldb-dotest --platform-name remote-linux --platform-url connect://172.17.0.2:1234 --platform-working-dir /tmp/test_lldb --arch aarch64 -p TestSVE*
```
The SVE tests are the ones that found https://github.com/llvm/llvm-project/issues/97537.

And everything works as expected. I don't normally run remote tests with `ninja check-lldb`, so I just ran the above command in a couple of terminals at the same time and there weren't any problems.

```
\_ ./lldb-server platform --server --listen 0.0.0.0:1234 --gdbserver-port 49140
    \_ lldb-server platform --child-platform-fd 9 --gdbserver-port 49140
    \_ lldb-server platform --child-platform-fd 9 --gdbserver-port 49140
    \_ /home/davspi01/lldb-server gdbserver  --fd=9 --native-regs
    |   \_ sh -c /usr/bin/lsb_release -i
    |       \_ /usr/bin/python3 -Es /usr/bin/lsb_release -i
    \_ /home/davspi01/lldb-server gdbserver  --fd=9 --native-regs
        \_ sh -c /usr/bin/lsb_release -i
            \_ /usr/bin/python3 -Es /usr/bin/lsb_release -i
```
Snapshot of the processes during that, all makes sense to me. Main platform, two connected clients and each one has spawned a gdbserver.



https://github.com/llvm/llvm-project/pull/104238