Does the cwd option work in an attach configuration?

[LarryNorth]

It seems that the cwd option in an attach launch configuration has no effect. I use docker-compose to run rdbg --open --port ... in a Docker container. When I run the corresponding attach launch configuration, rdbg tries to start the script in a folder that matches the vscode project folder on the host instead of the container's folder on which the project folder is mounted. Setting cwd to the container's folder has no effect. If the project's folder is mounted on an identically named folder (full path) in the container, it all works.

[ko1]

Which version do you use?

[LarryNorth]

1.5.0

[ko1]

with vscode-rdbg 0.0.9?

[ko1]

• cwd option is not supported on attach because cwd option is for "how to launch the debugger/debuggee".
• Using TCP/IP, all source access is by "Source" request and it doesn't open the source code in docker's filesystem. So I think you can see, but can not edit it. Correct?

When I run the corresponding attach launch configuration, rdbg tries to start the script in a folder that matches the vscode project folder on the host instead of the container's folder on which the project folder is mounted

"attach" doesn't run the debugger, but attach to already running Ruby process. So "rdbg tries to start the script" is not correct.

[LarryNorth]

Yes, with vscode-rdbg 0.0.9. The debug gem version is 1.5.0.

[LarryNorth]

The project folder is bind mounted in the Docker container. That folder's files can be seen and changed from the host and within the container.

rdbg --open --port ... is running in the container, not on the host. Something like the remoteWorkspaceRoot option that ruby-debug-ide uses in its vscode launch configuration may solve this problem. See the answer in this post.

[ko1]

Something like the remoteWorkspaceRoot option that ruby-debug-ide uses in its vscode launch configuration may solve this problem

Yes. Same as ruby/debug#463

[LarryNorth]

Yes. I my case the Docker container is ruby/debug#463's remote development machine. It seems that the rdbg vscode attach launch configuration would include the remote host, the remote port, and the remote source tree root. Here's an example from ruby-debug-ide:

        {
            "name": "Listen for rdebug-ide",
            "type": "Ruby",
            "request": "attach",
            "remoteHost": "127.0.0.1",
            "remotePort": "1234",
            "remoteWorkspaceRoot": "${workspaceRoot}"
        }

I am able to use rdbg now by bind mounting the local system's source tree root to the same location in the Docker container. (There's also some Docker port mapping involved.) There's no need for watchman or rsync because the local source tree's files and the those in the Docker container are the same physical files. ruby-debug-ide's remoteWorkspaceRoot option allows the source tree root to be mounted anywhere in the Docker container.

[firien]

From vscode #120307 I hacked together a demo of remoteWorkspaceRoot/remoteRoot from existing RdbgDebugAdapterTrackerFactory - translating source paths from VSCode <=> DA

remote-root-demo

You can test this locally with a simple ruby file. Make 2 copies of file, they should be named the same but live in different directories; like:

• /path/to/remote-demo/demo.rb
• /path/to/anywhere-else/demo.rb

From /path/to/remote-demo run rdbg demo.rb --open --port 12345.
Open /path/to/anywhere-else in vscode and launch debug with attach. Please note new remoteRoot, and localfs must be true

{
  "type": "rdbg",
  "name": "Attach with rdbg",
  "request": "attach",
  "debugPort": "12345",
  "localfs": true,
  "remoteRoot": "/path/to/remote-demo"
}

---

I have also installed this on remote vscode and verified it "works" within a rails Docker container. There are definitely issues with docker volumes not mapped locally.

---

1 bug I found locally was if you still have breakpoints set in vscode and detach - it will crash rdbg

---

This is by no means a finished product - just the bare minimum to get this working in my remote docker environment.

[firien]

1 bug I found locally was if you still have breakpoints set in vscode and detach - it will crash rdbg

This also crashes with the published vscode-rdbg, so maybe it's related to this issue in debug itself - ruby/debug#622

[firien]

I have also installed this on remote vscode and verified it "works" within a rails Docker container. There are definitely issues with docker volumes not mapped locally.

#29 (comment)

I cleaned up the code a lot and enabled multiple remote directory mappings in https://github.com/firien/vscode-rdbg/tree/multi-remote-root