debugging wrover-kit-v4.1 with extension does not hit break point in tasks (VSC-356)
See original GitHub issueDescribe the bug when using the extensions to debug a ESP-WROVER-KIT-V4.1 I can start a debug session however if my code creates a task with breakpoints in it, the break points are not hit. If I use my own launch.json it does work
To Reproduce create a project with the following code
#include <stdio.h>
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
void tsk(void* params)
{
while (true)
{
printf("Hello world!\n");
vTaskDelay(pdMS_TO_TICKS(1000));
}
}
void app_main(void)
{
xTaskCreate(tsk,"tsk",1024 *5,NULL,5,NULL);
}
add a break point in the app_main as well as inside the tasks while loop
Expected behavior both breakpoints should be hit
Screenshots please see video link here
**Environment **
- OS Name & Version: Windows 10
- VSCode Version: 1.45.1
- ESP-IDF Version: 4.0
- Python Version: 3.7
the launch.json that is wroking
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "ESP32 OpenOCD",
"type": "cppdbg",
"request": "launch",
"miDebuggerPath": "C:/esp/tools/.espressif/tools/xtensa-esp32-elf/esp-2019r2-8.2.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gdb.exe",
"cwd": "${workspaceFolder}/build",
//change the name of the elf file as required
"program": "C:/projects/spike/wrover/debug/build/debug.elf",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
},
{
"text": "file 'C:/projects/spike/wrover/debug/build/debug.elf'"
},
{
"text": "target remote 127.0.0.1:3333"
},
{
"text": "set remote hardware-watchpoint-limit 2"
},
{
"text": "monitor reset halt"
},
{
"text": "flushregs"
}
],
"externalConsole": false,
"logging": {
// "trace": true,
// "traceResponse": true,
//"engineLogging": true
}
}
]
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Troubleshoot Breakpoints in the Visual Studio Debugger
This section provides information to troubleshoot issues when the debugger isn't displaying any warnings – the breakpoint is a solid red circle ...
Read more >Test Web: first breakpoint in extension not always hit #83583
Start debugging. You can hit breakpoints. Reload current page. Start debugging. You still see the breakpoints there, but cannot hit it.
Read more >Debugging SSIS Script task - Breakpoint is enabled but it does ...
The break point has no conditions on it, so I expect it to hit every time the package runs. I am using Visual...
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 >Training - Debugger Basics - Lauterbach
Intrusive TASK-aware Breakpoint ... Depending on the processor architecture different debug features are ... Full parameter syntax which is not in use.
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
Hi Brian,
debug.log
Please find attached zipped project (without the build folder) hello_world.zip
The ESP-IDF Debug Adapter looks as follows
This issue has been marked as
stale
since there are no activities, and this will be closed in 5 days if there are no further activities