[lldb-dev] Remote debugging - unix socket and/or specific port

[Mark Nelson via lldb-dev]

Has there been any change in this since reported here :

http://lists.llvm.org/pipermail/lldb-dev/2016-June/010616.html

It is pretty clear that that the remote-linux platform is trying to open
additional ports to talk to lldb-server, and if that server is in a
container we need to expose them. But what ports, how many, how to specify?
All uncertain.

Looking at the source shows there are some (undocumented?) port commands in
lldb-server platform, I'm wondering if this is a solved problem that just
doesn't have an easy-to-search-for solution.

BTW, I may be barking up the wrong tree. I am using lldb on the host and
lldb-server on the remote, so the gdb-server protocol shouldn't be in play,
at least I don't think so.

But the problem I see in this configuration sure looks to be one of ports
being firewalled.

>Hi Adrien,
>
>I think your diagnosis is correct here. LLDB does indeed create an
>additional connection to the gdb-server instance which is started by the
>platform instance when you start debugging. In case of android platforms we
>already include code to forward this port automatically, but there is no
>such thing for linux -- we just expect the server to be reachable.


------------------------------------------------------------------------------

Mark Nelson – markn at ieee.org
<https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=markn@ieee.org> -
http://marknelson.us
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20170724/34598b9d/attachment.html>