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.
Debuger has broken
See original GitHub issueDescribe the bug After the latest update when I start my application in debug mode I don’t see any call stack and no breakpoint is working.
To Reproduce Steps to reproduce the behavior:
- Go to ‘1.47.1’ version
- Start any application in debug mode
- See error
Log File
VS Code Version: 1.47.1
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
VS2019 Debugger BROKEN - Visual Studio Feedback
Something about the way the debugger maps source code to data values is VERY broken! Yesterday I was trying to debug the function...
Read more >Debugging is Broken - Here's How To Fix It - DevOps.com
Debugging is broken. But with a few key changes, debugging can be a much more manageable and predictable process.
Read more >Troubleshoot Breakpoints in the Visual Studio Debugger
When debugging, a breakpoint has two possible visual states: ... Break (C#/VB) or __debugbreak (C++) to the line of code where you're trying ......
Read more >debugger is broken - on breakpoint it hangs saying "collecting ...
debugger is broken - on breakpoint it hangs saying "collecting data...". This is so bad will have to use revert to a different...
Read more >Fixing Broken Debugger Extensions - OSR
Fixing Broken Debugger Extensions. As I'm sure you're all aware at this point, there are two different sets of PDB files generated for...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Naresh-varma thanks for the confirmation – see the issue I linked
@XyFreak see here https://github.com/microsoft/vscode/issues/102035#issuecomment-656801666
A fix for this issue has now been released in VS Code 1.47.2. If you previously had to opt-out of the new debugger, you should be safe to turn it back on. Thanks again for the report!