Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for path mapping for remote debugging #1289

Closed
DonJayamanne opened this issue Apr 3, 2018 · 0 comments · Fixed by #1300
Closed

Add support for path mapping for remote debugging #1289

DonJayamanne opened this issue Apr 3, 2018 · 0 comments · Fixed by #1300
Assignees
Milestone

Comments

@DonJayamanne
Copy link

DonJayamanne commented Apr 3, 2018

In the current version of the debugger we have the ability to map just two paths:

        {
            "name": "Attach",
            "type": "pythonExperimental",
            "request": "attach",
            "localRoot": "${workspaceFolder}",
            "remoteRoot": "${workspaceFolder}",
            "port": 9091,
            "host": "157.54.167.255"
        }

However the new debugger has the ability to map multiple paths.
I can see this being used when debugging std libs.
I.e. we'd need to map paths in workspace as well as paths in the interpreter.

My suggestion is to leave the existing path mapping as is, but introduce an additional property for more path mappings as follows.
@brettcannon What do you think about this approach?

        {
            "name": "Attach",
            "type": "pythonExperimental",
            "request": "attach",
            "localRoot": "${workspaceFolder}",
            "remoteRoot": "${workspaceFolder}",
             "pathMappings": [
                    { "localRoot": "C:\\Program Files\\Python26\\xxx",
                    "remoteRoot": "/usr/bin/python/xxx"} ,
            ], 
            "port": 9091,
            "host": "157.54.167.255"
        }
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant