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

2017-07-28 Thread Howard Hellyer via lldb-dev
"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 been any change in this since reported here : > > http

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

2017-07-27 Thread Eugene Zemtsov via lldb-dev
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

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

2016-07-07 Thread Adrien Duermael via lldb-dev
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

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

2016-06-29 Thread Pavel Labath via lldb-dev
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