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

Mark Nelson via lldb-dev lldb-dev at lists.llvm.org
Fri Jul 28 04:51:53 PDT 2017

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

>Date: Thu, 27 Jul 2017 19:22:46 -0700
>From: Eugene Zemtsov via lldb-dev <lldb-dev at lists.llvm.org>
>To: Mark Nelson <markn at ieee.org>
>Cc: lldb-dev at 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 – markn at ieee.org - http://marknelson.us
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20170728/28b669a2/attachment.html>

More information about the lldb-dev mailing list