[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 – ma...@ieee.org
 -
http://marknelson.us
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-dev Digest, Vol 86, Issue 26

[Mark Nelson via lldb-dev]

Thanks for the verification Eugene.


I guess for the short term I am going to look at hacking the source to
force the use of a specific port - this might get us around the blocking
issue.


>Date: Thu, 27 Jul 2017 19:22:46 -0700
>From: Eugene Zemtsov via lldb-dev 
>To: Mark Nelson 
>Cc: lldb-dev@lists.llvm.org
>Subject: Re: [lldb-dev] Remote debugging - unix socket and/or specific port
>
>Hi Mark,
>
>A quick look at PlatformPOSIX.cpp, PlatformLinux.cpp
>and PlatformRemoteGDBServer.cpp shows that Pavel's description of port
>forwarding situation is still accurate. On Linux currently there is no way
>to know the port number before LLDB tries actually attach to something.
>
>Mentioning of GDB server protocol shouldn't confuse you, it's just a name
>of a text protocol LLDB client uses to talk to LLDB server [1]. LLDB tries
>to be compatible with GDB in this aspect.
>
>
>[1] https://sourceware.org/gdb/onlinedocs/gdb/Remote-Protocol.html


--

Mark Nelson – ma...@ieee.org - http://marknelson.us
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev