Skip to content

Remote debugging fails due to incorrect path mappings #5075

Closed

Description

@EsmeAioli

Environment data

  • VS Code version: 1.32.3
  • Extension version (available under the Extensions sidebar): 2019.3.6215
  • OS and version: Windows_NT x64 10.0.16299, Ubuntu 18.04
  • Python version (& distribution if applicable, e.g. Anaconda): 3.6.7
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv

Expected behaviour

Pydev should be able to resolve the paths fine and start debugging

Actual behaviour

pydev debugger: warning: trying to add breakpoint to file that does not exist: /mnt/c/Users/limxuan/Desktop/PYTHON Entity Graph Webapp/Dependency_Grapher/C:/Users/limxuan/Desktop/PYTHON Entity Graph Webapp/Dependency_Grapher/graph_handler.py (will have no effect)

Steps to reproduce:

  1. Have this in your launch.json:

     {
         "name": "Python: Remote Attach",
         "type": "python",
         "request": "attach",
         "port": 5678,
         "host": "127.0.0.1",
         "pathMappings": [
             {
                 "localRoot": "${workspaceFolder}",
                 "remoteRoot": "."
             }
         ]
     }
    

Logs

Nothing exciting, so I won't post it

Apologies if there are duplicates, didn't catch any when I ran this

Activity

  1. ghost added
    triage-neededNeeds assignment to the proper sub-team
    on Apr 2, 2019
  2. ghost removed
    triage-neededNeeds assignment to the proper sub-team
    on Apr 2, 2019
  3. changed the title [-][WSL] Pydev uses Windows locations instead of Linux[/-] [+]Pydev uses Windows locations instead of Linux[/+] on Apr 4, 2019
  4. changed the title [-]Pydev uses Windows locations instead of Linux[/-] [+]Debugger uses Windows locations instead of Linux[/+] on Apr 4, 2019
  5. changed the title [-]Debugger uses Windows locations instead of Linux[/-] [+]Remote debugging fails due to incorrect path mappings[/+] on Apr 4, 2019
  6. DonJayamanne commented on May 22, 2019

    @DonJayamanne

    Upstream issue has been resolved.

  7. locked as resolved and limited conversation to collaborators on May 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-debuggingbugIssue identified by VS Code Team member as probable bug

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions