Running app through lldb-server hijacks attempts at opening ports

I'm having issues with lldb-server seemingly eating attempts at port opening on the debugged app, the app reporting "DreamDaemon FAILED to open port 52514".
The app in question works fine when not launched through lldb, and firewall exceptions for both it and lldb are in place (for both public and private networks).

Grepping netstat for the port in question also doesn't show anything, only if running the app standalone does an entry show up (picture shows different ports for demonstration, but even if assigning port 0 (pick any available) this behaviour doesnt change).

The exact setup is a qemu VM running windows 10, which runs `lldb-server.exe platform --listen "*:1234" --server` in an elevated powershell, and the host machine running linux, running
```
lldb
> platform select remote-windows
> platform connect connect://192.168.122.101:1234
> target create --remote-file "C:\Program Files (x86)\BYOND\bin\dreamdaemon.exe"
> run
```

Reproduce the reported setup with lldb-server.exe on the Windows 10 QEMU guest and the remote-windows LLDB commands shown in the issue. Compare port-opening behavior with standalone DreamDaemon execution and inspect the netstat results. Done means identifying why the debugged app cannot open its port remotely, or documenting the limitation and a verified workaround.

Written by the indexing model from the issue text.