"lldb-dev" wrote on 24/07/2017 16:19:19:
> From: Mark Nelson via lldb-dev
> To: lldb-dev@lists.llvm.org
> Date: 24/07/2017 16:19
> Subject: [lldb-dev] Remote debugging - unix socket and/or specific port
> Sent by: "lldb-dev"
>
> Has there be
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
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
Hi Pavel,
Thanks for your answer! At least I know it’s not supposed to work as is.
I’ll see if I can do something similar to what you guys did for Android
platforms.
Thanks again!
Cheers,
- Adrien Duermael
> On Jun 29, 2016, at 5:07 AM, Pavel Labath wrote:
>
> Hi Adrien,
>
> I think yo
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 n
Hi,
I’ve been trying to run lldb-server from within a linux container lately.
When I try to attach from outside the container using lldb command, most steps
are successful but I can’t launch the process:
platform select remote-linux 👍
platform connect connect://IP:PORT 👍
target create main 👍
Hi,
I’ve been trying to run lldb-server from within a linux container lately.
When I try to attach from outside the container using lldb command, most steps
are successful but I can’t launch the process:
platform select remote-linux 👍
platform connect connect://IP:PORT 👍
target create main 👍
