You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the template for launch.json comes up with something similar to
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Python: Remote Attach",
"type": "python",
"request": "attach",
"connect": {
"host": "localhost",
"port": 5678
},
"pathMappings": [
{
"localRoot": "${workspaceFolder}",
"remoteRoot": "."
}
],
"justMyCode": true
}
]
}
But with a development setup (i.e. slicer built from source) the pathMappings parameter here might the debugger from stepping into slicer python code, this might also be a problem how i set up the workspace though, but removing the pathMappings entry allowed stepping into the base slicer python
The text was updated successfully, but these errors were encountered:
Any suggestions for improving the documentation is welcome but probably we would need to somewhow change this setting automatically or find a way to make things work with the default path mapping.
Currently the template for
launch.json
comes up with something similar toBut with a development setup (i.e. slicer built from source) the
pathMappings
parameter here might the debugger from stepping into slicer python code, this might also be a problem how i set up the workspace though, but removing thepathMappings
entry allowed stepping into thebase
slicer pythonThe text was updated successfully, but these errors were encountered: