[lldb-dev] [Bug 45669] New: I would like to control the remote communication port

via lldb-dev lldb-dev at lists.llvm.org
Sat Apr 25 11:30:55 PDT 2020


https://bugs.llvm.org/show_bug.cgi?id=45669

            Bug ID: 45669
           Summary: I would like to control the remote communication port
           Product: lldb
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: All Bugs
          Assignee: lldb-dev at lists.llvm.org
          Reporter: maxime.roussinbelanger at gmail.com
                CC: jdevlieghere at apple.com, llvm-bugs at lists.llvm.org

Hello!

I would like to debug my target (which is at home), from my remote work
computer while being at home through a VPN.

>From home I connect to my workstation through the VPN and create an ssh tunnel  
(ssh config: `RemoteForward localhost:10000 TARGET_LAN_IP:10000`).

But when I try to attach to the running application on the target it
dynamically allocates a port and tries to reach the server to that port.
Unfortunately, this is not possible because of the ssh tunnel. I can however do
: `platform connect connect://localhost:10000`, but I cannot go into debugging.

SSH tunnelling doesn't support, as far as I know, ranges of RemoteForward
ports.

Is there a way to control the port that is dynamically allocated? I found a
"similar" issue of 4 years ago: (I'm not inside a container, but the idea is
the same)

http://lists.llvm.org/pipermail/lldb-dev/2016-June/010616.html

I'm wondering if the situation is still the same and the port cannot be set
manually?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20200425/a6eb5a13/attachment-0001.html>


More information about the lldb-dev mailing list