question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Debugger source map incorrect for multiple debuggers attached

See original GitHub issue

Hi! since the last update to 1.47.0 at the 11.7.2020, attaching debuggers to multiple docker containers stopped working: We attach to multiple docker containers by:

 {
            "type": "node",
            "request": "attach",
            "name": "Attach[MICROSERVICENAME]",
            "port": MICROSERVICEPORT,
            "restart": true,
            "address": "localhost",
            "localRoot": "${workspaceFolder}/MICROSERVICENAME",
            "protocol": "inspector",
            "remoteRoot": "/usr/src/app"
        }

Without setting any breakpoints, everything works fine. If I add a breakpoint somewhere in the code, the debugger stops at “random” positions in the code. These positions are always the same, depending on the breakpoint, but in completely different files. Also adding a breakpoint in microservice2 in debugmode, without attaching to it causes the debugger of microservice1 to stop at non existing breakpoints.

VS Code Version: 1.47.1 (1.48.0 has the same error) vscode-debugadapter-microservice1.gz vscode-debugadapter-microservice2.json.gz

EDIT Downgraded vscode to version 1.46.1 and everything works fine again

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
connor4312commented, Jul 15, 2020

Thanks, looking at this. You can set debug.javascript.usePreview: false to skip using the new debugger on the latest VS Code version.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Could not read source map error and few other errors while ...
When I am trying to debug and test the changes locally, I am getting many errors in the debug console related to source...
Read more >
Why does my debugger stop visually at the wrong line?
The behavior is the same within the WebStorm internal debugger. So I think it is not Chrome's fault. It looks like the source...
Read more >
How to Debug Node.js Code Using Multiple Tools - Kinsta
This tutorial demonstrates various tools to debug node applications and find their root causes. Dig in and learn from the ground up.
Read more >
Troubleshooting common PHP debugging issues | PhpStorm ...
In some cases, the debugger can connect, but you get the error messages indicating that no mapping between the remote and project files...
Read more >
Navigate through code by using the Visual Studio debugger
Learn how to use the Visual Studio debugger to troubleshoot your code. ... the Run To Cursor command to start the app, debugger...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found