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.
Debug Button Doesn't Work
See original GitHub issueBrief Issue Summary
The debug button doesn’t work in vscode-remote inside containers.
Expected:
Show a list of tragets to select for debug.
Apparent Behavior:
Show error message below:
Failed to prepare executable target with name 'undefined'
Platform and Versions
- Operating System:
- CMake Version: 3.18.1
- VSCode Version: 1.48.0
- CMake Tools Extension Version: 1.4.1
- Compiler/Toolchain: gcc7.5
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Run/debug button is enabled but does not work
Try re-creating configuration from scratch, try re-creating project configuration files by re-importing it from existing sources (File | New | ...
Read more >Running test by clicking "Run | Debug" button doesn't work
Running the app however, behave perfectly normal. ... Steps to reproduce the behavior: Go to test/; Click on any Run / Debug on...
Read more >Debug button not working! (Visual basic express 2010)
The debug button in visual basic doesn't run the program that I developed. I tried: Changed to expert mode --> changed to exceptions...
Read more >Debugging in Visual Studio Code
VS Code maintains a debug session while the program is running, and pressing the Stop button terminates the program. Tip: The Run action...
Read more >Can not press run-button after debugging - TI E2E
You need the proper Debug context selected in the Debug view. Please click on the last node in the Debug view ("Texas Instruments...
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
This happened when I made a mistake in CMakeList.txt:
set(CMAKE_BUILD_TYPE DEBUG). Change toset(CMAKE_BUILD_TYPE Debug)fixed the issue 😂.I made it work by making sure that it is
Debugrather thanDEBUG, (setting"cmake.loggingLevel": "debug"in.vscode/settings.jsonto get verbose logs), deleting<cmake_build_folder>/.cache, then reload vscode window, then runset debug targetwhich asks me for the target, as expected.