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
It stops on preset breakpoint of some virtual files with remote paths, not existing locally. Files it steps on based on original files but may contain some transformations (e.g. source map comments)
Expected behavior
Break point should trigger at my local file, exactly where I put it. All paths in debugger should be replaced by remoteRoot=>localRoot rule according to launch.json configuration
Screenshots
Setting breakpoint before debugging:
Breakpoint triggered:
remote paths in Loaded Scripts, it also ignores the skipFiles of debug configuration:
Versions
vscode: 1.96.2 deno: 2.1.4 extension: 3.43.2
The text was updated successfully, but these errors were encountered:
pmunin
changed the title
Remote Debugger does not do remoteRoot=>localRoot mappings
Remote Debugger does not do remoteRoot=>localRoot source mappings
Jan 8, 2025
Describe the bug
Debugging by attaching to remote host does not do remotePath=>localPath transformations. inspector-brk|wait still reveals remote paths
To Reproduce
docker-compose.yml:
.vscode/launch.json/configurations:
deno.json:
Start docker compose
Launch debug configuration
It stops on preset breakpoint of some virtual files with remote paths, not existing locally. Files it steps on based on original files but may contain some transformations (e.g. source map comments)
Expected behavior
Break point should trigger at my local file, exactly where I put it. All paths in debugger should be replaced by remoteRoot=>localRoot rule according to launch.json configuration
Screenshots
Setting breakpoint before debugging:
Breakpoint triggered:
remote paths in Loaded Scripts, it also ignores the skipFiles of debug configuration:
Versions
vscode: 1.96.2 deno: 2.1.4 extension: 3.43.2
The text was updated successfully, but these errors were encountered: