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 <lldb-dev@lists.llvm.org> >To: Mark Nelson <ma...@ieee.org> >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
