Can not start debugger (VSC-265)
See original GitHub issueI have a problem to start debugger. OpenOCD is running, but the debugger stops almost immediatelly after the green arrow is pressed. Unfortunatelly no output is printed in either console. There is probably problem with the ${command:espIdf.getProjectName} variable. I have tried to find workaround and the following is working. Also there is needed to run xtensa-esp32-elf-gdb.exe under the windows.
launch.json
"miDebuggerPath": "xtensa-esp32-elf-gdb",
"program": "${workspaceFolder}/build/app-template.elf",
"windows": {
"miDebuggerPath": "xtensa-esp32-elf-gdb.exe",
"program": "${workspaceFolder}\\build\\app-template.elf",
},
Extension 0.1.4 vscode 1.43.1 python 3.8.1 Windows 10
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
cannot start debugging because the debug target is missing ...
Right click on the Visual Studio Project - Properties - Debug - (Start Action section) - select "Start project" radio button.
Read more >Debugging in Visual Studio Code
One of the great things in Visual Studio Code is debugging support. Set breakpoints, step-in, inspect variables and more.
Read more >Visual Studio cannot start debugging because the debug target
This video is not fake works 100%It can fix or solve the same problem if you ecounter some errors in c# programming languages...
Read more >VS Code Debugger not working for python - Microsoft Q&A
It seems when I do Run->"start Debugging' no command comes to terminal. Any VS Code log file that I can look at to...
Read more >Debugging in VS Code suddenly stopped working
Uninstalling and reinstalling VS Code;; Uninstalling and reinstalling Julia;. All of the above while using Linux Mint. After all that I decided to...
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 FreeTop 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
Top GitHub Comments
The new version 0.2.0 has a few issues with debugging. Clicking “Launch” does not start OpenOCD, even with “mode” set to “auto”, or not set at all. That line in launch.json also gives an error that “auto” must be an enum. https://github.com/espressif/vscode-esp-idf-extension/blob/8c4e10d9e1c4182265dc9c050c0d1bf617745427/package.json#L425 file has “mode” set to “enum”, I think it should be “string”. (Changing it to string, it still does not work, but no error.)
I can get it to work if I click the task “OpenOCD: Start OpenOCD”, then click “Launch”, but only if “mode” is not set at all. With the “mode” option set to either option, esp_debug_adapter does not start unless I also start “apapter” manually. I get a toast message the says “OpenOCD Exit with non-zero error code 1”.
I’ll attach my log file.
esp_idf_vsc_ext.log
Issue is marked as stale since there are no activities.